linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	NeilBrown <neilb@suse.com>
Subject: Re: linux-next: build warning after merge of the nfsd tree
Date: Sun, 2 Apr 2017 22:39:34 -0400	[thread overview]
Message-ID: <20170403023934.GB19658@fieldses.org> (raw)
In-Reply-To: <20170403110948.3ca5ab8b@canb.auug.org.au>

On Mon, Apr 03, 2017 at 11:09:48AM +1000, Stephen Rothwell wrote:
> Hi,
> 
> After merging the nfsd tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
> 
> fs/nfsd/nfs4state.c: In function 'copy_cred':
> fs/nfsd/nfs4state.c:1917:6: warning: unused variable 'ret' [-Wunused-variable]
>   int ret;
>       ^
> 
> Introduced by commit
> 
>   d39662236bf8 ("nfsd4: remove pointless strdup_if_nonnull")
> 
> Also, that commit has no Signed-off-by from its Author.

Both fixed, thanks.--b.

  reply	other threads:[~2017-04-03  2:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03  1:09 linux-next: build warning after merge of the nfsd tree Stephen Rothwell
2017-04-03  2:39 ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-15  9:27 Stephen Rothwell
2022-02-15 15:08 ` Chuck Lever III
2018-05-10  0:42 Stephen Rothwell
2018-05-10 14:21 ` Chuck Lever
2018-05-10 15:24   ` Bruce Fields
2018-05-10 16:10     ` Chuck Lever
2018-01-18 23:23 Stephen Rothwell
2011-03-10  0:53 Stephen Rothwell
2011-03-17 18:09 ` J. Bruce Fields

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=20170403023934.GB19658@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=sfr@canb.auug.org.au \
    /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).