>>> On 5/19/2010 at 11:42 AM, in message <20100520014225.e4343903.sfr@xxxxxxxxxxxxxxxx>, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi Gregory, > > On Wed, 31 Mar 2010 05:51:28 -0600 "Gregory Haskins" <ghaskins@xxxxxxxxxx> > wrote: >> >> >>> On 3/29/2010 at 01:52 PM, in message >> <1269885165-18617-7-git-send-email-tj@xxxxxxxxxx>, Tejun Heo <tj@xxxxxxxxxx> >> wrote: >> > Implicit slab.h inclusion via percpu.h is about to go away. Make sure >> > gfp.h or slab.h is included as necessary. >> > >> > Signed-off-by: Tejun Heo <tj@xxxxxxxxxx> >> > Cc: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> >> > Cc: Gregory Haskins <ghaskins@xxxxxxxxxx> >> >> Thanks Tejun, >> >> Acked-by: Gregory Haskins <ghaskins@xxxxxxxxxx> >> >> (will add to my tree) > > It never made it as far as I can see ... maybe something equivalent went in. Hi Steven, I dropped the ball on this. Will merge when I return from lunch. -Greg > > From: Tejun Heo <tj@xxxxxxxxxx> > To: sfr@xxxxxxxxxxxxxxxx, linux-next@xxxxxxxxxxxxxxx, > linux-kernel@xxxxxxxxxxxxxxx > Cc: Tejun Heo <tj@xxxxxxxxxx>, Gregory Haskins <ghaskins@xxxxxxxxxx> > Subject: [PATCH 06/17] vbus: update gfp/slab.h includes > Date: Tue, 30 Mar 2010 02:52:34 +0900 > > Implicit slab.h inclusion via percpu.h is about to go away. Make sure > gfp.h or slab.h is included as necessary. > > Signed-off-by: Tejun Heo <tj@xxxxxxxxxx> > Cc: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> > Cc: Gregory Haskins <ghaskins@xxxxxxxxxx> > --- > drivers/vbus/pci-bridge.c | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/drivers/vbus/pci-bridge.c b/drivers/vbus/pci-bridge.c > index 0d51324..36de7c4 100644 > --- a/drivers/vbus/pci-bridge.c > +++ b/drivers/vbus/pci-bridge.c > @@ -22,6 +22,7 @@ > #include <linux/pci.h> > #include <linux/mm.h> > #include <linux/workqueue.h> > +#include <linux/slab.h> > #include <linux/debugfs.h> > #include <linux/seq_file.h> > #include <linux/ioq.h -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html