All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bart Van Assche <bart.vanassche@wdc.com>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: linux-next: build warning after merge of the rdma tree
Date: Thu, 26 Jul 2018 10:55:53 +1000	[thread overview]
Message-ID: <20180726105553.00a36e3c@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

Hi all,

After merging the rdma tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:

net/sunrpc/xprtrdma/svc_rdma_rw.c: In function 'svc_rdma_post_chunk_ctxt':
net/sunrpc/xprtrdma/svc_rdma_rw.c:350:5: warning: 'bad_wr' may be used uninitialized in this function [-Wmaybe-uninitialized]
  if (bad_wr != first_wr)
     ^

Introduced by commit

  ed288d74a9e5 ("net/xprtrdma: Simplify ib_post_(send|recv|srq_recv)() calls")

This is an actual problem.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2018-07-26  0:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  0:55 Stephen Rothwell [this message]
2018-07-26  3:05 ` linux-next: build warning after merge of the rdma tree Jason Gunthorpe
2018-07-26  5:10   ` Bart Van Assche
2018-07-26 17:38     ` Jason Gunthorpe
  -- strict thread matches above, loose matches on Subject: below --
2021-02-10 10:11 Stephen Rothwell
2021-02-10 13:47 ` Jason Gunthorpe
2021-02-10 17:17   ` Nathan Chancellor
2021-02-10 22:08   ` Lee Jones
2020-12-03  7:42 Stephen Rothwell
2020-12-03  9:39 ` Leon Romanovsky
2019-02-14  0:23 Stephen Rothwell
2019-02-14  0:18 Stephen Rothwell
2019-02-14  0:21 ` Doug Ledford
2019-02-14 12:35   ` Wan, Kaike
2018-07-10  1:28 Stephen Rothwell
2018-05-06 23:44 Stephen Rothwell
2018-05-14 18:03 ` Jason Gunthorpe
2018-05-14 18:09   ` Steve Wise
2018-05-14 20:29     ` Steve Wise
2018-05-06 23:40 Stephen Rothwell

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=20180726105553.00a36e3c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bart.vanassche@wdc.com \
    --cc=chuck.lever@oracle.com \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.