Subject: + cmdline-parser-fix-build.patch added to -mm tree
To: a.beregalov@xxxxxxxxx,alexander.beregalov@xxxxxxxxx,caizhiyong@xxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Thu, 14 Nov 2013 12:35:39 -0800
The patch titled
Subject: cmdline-parser: fix build
has been added to the -mm tree. Its filename is
cmdline-parser-fix-build.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/cmdline-parser-fix-build.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/cmdline-parser-fix-build.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Alexander Beregalov <a.beregalov@xxxxxxxxx>
Subject: cmdline-parser: fix build
Fix following errors:
include/linux/cmdline-parser.h:17:12: error: 'BDEVNAME_SIZE' undeclared here
block/cmdline-parser.c:17:2: error: implicit declaration of function 'kzalloc'
Signed-off-by: Alexander Beregalov <alexander.beregalov@xxxxxxxxx>
Cc: CaiZhiyong <caizhiyong@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/cmdline-parser.h | 2 ++
1 file changed, 2 insertions(+)
diff -puN include/linux/cmdline-parser.h~cmdline-parser-fix-build include/linux/cmdline-parser.h
--- a/include/linux/cmdline-parser.h~cmdline-parser-fix-build
+++ a/include/linux/cmdline-parser.h
@@ -8,6 +8,8 @@
#define CMDLINEPARSEH
#include <linux/blkdev.h>
+#include <linux/fs.h>
+#include <linux/slab.h>
/* partition flags */
#define PF_RDONLY 0x01 /* Device is read only */
_
Patches currently in -mm which might be from a.beregalov@xxxxxxxxx are
cmdline-parser-fix-build.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
