On Fri, Jul 27, 2012 at 03:53:03PM +0100, Mel Gorman wrote: > On Fri, Jul 27, 2012 at 10:27:32PM +0800, Fengguang Wu wrote: > > On Fri, Jul 27, 2012 at 03:10:36PM +0100, Mel Gorman wrote: > > > On Fri, Jul 27, 2012 at 09:02:25PM +0800, Fengguang Wu wrote: > > > > Hi Mel, > > > > > > > > There are new sparse warnings show up in > > > > > > > > tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm > > > > head: 247109fa112ac912f31efc28e130ed2a0cc1764c > > > > commit: 5bb176c86a868289d5d93d89919c3b5a339d6d20 [147/308] nfs: enable swap on NFS > > > > > > > > > > Thanks (adding Andrew to cc for picking up in mm) > > > > > > How about the following? > > > > Looks good to me. And it does fix the warning. > > > > I assume the fix will be folded into the original patch, otherwise the > > subject will look a bit strange ;) > > > > That's what I'm expecting. I've sent a few fixes marked "buildfix: > patch subject" so Andrew knows exactly which patches to fold together. > Ordinarily when dealing with just mmotm I would specify the filename in > the quilt series but that does not make as much sense when talking about > linux-next. Ah yes! That title is actually pretty readable and precise for Andrew. Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
