[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20100329162825.a233ce8e.sfr@canb.auug.org.au>
Date: Mon, 29 Mar 2010 16:28:25 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Tejun Heo <tj@...nel.org>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Daniel Mack <daniel@...aq.de>, Takashi Iwai <tiwai@...e.de>
Subject: linux-next: build failure after merge of the slabh tree
Hi Tejun,
After merging the slabh tree, today's linux-next build (x86_64
allmodconfig) failed like this:
sound/usb/quirks.c: In function 'create_fixed_stream_quirk':
sound/usb/quirks.c:136: error: implicit declaration of function 'kmalloc'
sound/usb/quirks.c:136: warning: assignment makes pointer from integer without a cast
sound/usb/quirks.c:138: error: implicit declaration of function 'kfree'
sound/usb/quirks.c: In function 'create_uaxx_quirk':
sound/usb/quirks.c:223: warning: assignment makes pointer from integer without a cast
Caused by commit d103d3b3e8512312b5254950035366d4422a479a ("percpu: don't
implicitly include slab.h from percpu.h") from the slabh tree interacting
with commit e5779998bf8b70e48a6cc208c8b61b33bd6117ea ("ALSA: usb-audio:
refactor code") from the sound tree.
I applied the following merge fixup patch which should be applied to the
sound tree (see Documentation/SubmitChecklist Rule #1 :-)).
From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Mon, 29 Mar 2010 16:08:03 +1100
Subject: [PATCH] sound: quirks: use of kmalloc/kfree requires the include of slab.h
Signed-off-by: Stephen Rothwell <sfr@...b.auug.org.au>
---
sound/usb/quirks.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
index d4ced64..136e5b4 100644
--- a/sound/usb/quirks.c
+++ b/sound/usb/quirks.c
@@ -15,6 +15,7 @@
*/
#include <linux/init.h>
+#include <linux/slab.h>
#include <linux/usb.h>
#include <linux/usb/audio.h>
--
1.7.0.3
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists