From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: linux-next: build warning after merge of the nfsd tree
Date: Thu, 10 May 2018 10:42:13 +1000 [thread overview]
Message-ID: <20180510104213.31c41377@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
Hi all,
After merging the nfsd tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
net/sunrpc/xprtrdma/svc_rdma_transport.c: In function 'rdma_listen_handler':
net/sunrpc/xprtrdma/svc_rdma_transport.c:299:23: warning: unused variable 'rdma' [-Wunused-variable]
struct svcxprt_rdma *rdma = cma_id->context;
^~~~
Introduced by commit
d1ab72afe681 ("svcrdma: Trace key RDMA API events")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-05-10 0:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 0:42 Stephen Rothwell [this message]
2018-05-10 14:21 ` linux-next: build warning after merge of the nfsd tree Chuck Lever
2018-05-10 15:24 ` Bruce Fields
2018-05-10 16:10 ` Chuck Lever
-- 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-01-18 23:23 Stephen Rothwell
2017-04-03 1:09 Stephen Rothwell
2017-04-03 2:39 ` J. Bruce Fields
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=20180510104213.31c41377@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).