linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	Jason Gunthorpe <jgg@mellanox.com>,
	"dledford@redhat.com" <dledford@redhat.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"leon@kernel.org" <leon@kernel.org>
Subject: Re: linux-next: build warning after merge of the mlx5-next tree
Date: Wed, 18 Mar 2020 02:31:17 +0000	[thread overview]
Message-ID: <a6612dbf3cd0ecdde7c0e4c8d35ebf470e2cf346.camel@mellanox.com> (raw)
In-Reply-To: <20200318130531.1df149c7@canb.auug.org.au>

On Wed, 2020-03-18 at 13:05 +1100, Stephen Rothwell wrote:
> Hi all,
> 
> On Mon, 16 Mar 2020 10:39:13 +1100 Stephen Rothwell <
> sfr@canb.auug.org.au> wrote:
> > Hi all,
> > 
> > After merging the mlx5-next tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> > 
> > In file included from include/linux/printk.h:331,
> >                  from include/linux/kernel.h:15,
> >                  from
> > drivers/net/ethernet/mellanox/mlx5/core/mr.c:33:
> > drivers/net/ethernet/mellanox/mlx5/core/mr.c: In function
> > 'mlx5_core_create_mkey':
> > include/linux/dynamic_debug.h:157:25: warning: 'key' may be used
> > uninitialized in this function [-Wmaybe-uninitialized]
> >   157 |  _dynamic_func_call(fmt,__dynamic_dev_dbg,   \
> >       |                         ^~~~~~~~~~~~~~~~~
> > drivers/net/ethernet/mellanox/mlx5/core/mr.c:47:5: note: 'key' was
> > declared here
> >    47 |  u8 key;
> >       |     ^~~
> > 
> > Probably introduced by commit
> > 
> >   fc6a9f86f08a ("{IB,net}/mlx5: Assign mkey variant in mlx5_ib
> > only")
> 
> This warning now appears in the rdma tree.
> 

thanks Stephen,

actuall a fix patch was merged yesterday into mlx5-next [1]

and should already be in linux-next build, and will soon land in rdma
tree.

Thanks,
Saeed.

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/commit/?h=mlx5-next&id=826096d84f509d95ee8f72728fe19c44fbb9df6b

  reply	other threads:[~2020-03-18  2:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 23:39 linux-next: build warning after merge of the mlx5-next tree Stephen Rothwell
2020-03-18  2:05 ` Stephen Rothwell
2020-03-18  2:31   ` Saeed Mahameed [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-05  2:07 Stephen Rothwell
2019-11-05 14:38 ` Leon Romanovsky

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=a6612dbf3cd0ecdde7c0e4c8d35ebf470e2cf346.camel@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).