From: Mel Gorman <mgorman@suse.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [next:akpm 147/308] net/sunrpc/clnt.c:720:36: sparse: dereference of noderef expression
Date: Fri, 27 Jul 2012 14:53:03 +0000 [thread overview]
Message-ID: <20120727145303.GF612@suse.de> (raw)
In-Reply-To: <20120727130225.GA29912@localhost>
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.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2012-07-27 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 13:02 [next:akpm 147/308] net/sunrpc/clnt.c:720:36: sparse: dereference of noderef expression Fengguang Wu
2012-07-27 14:10 ` Mel Gorman
2012-07-27 14:27 ` Fengguang Wu
2012-07-27 14:53 ` Mel Gorman [this message]
2012-07-27 15:01 ` Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120727145303.GF612@suse.de \
--to=mgorman@suse.de \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).