public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Lee Jones <lee.jones@linaro.org>,
	Doug Ledford <dledford@redhat.com>,
	Leon Romanovsky <leonro@nvidia.com>,
	Parav Pandit <parav@nvidia.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the rdma tree
Date: Wed, 10 Feb 2021 10:17:22 -0700	[thread overview]
Message-ID: <20210210171722.GA1670976@ubuntu-m3-large-x86> (raw)
In-Reply-To: <20210210134742.GY4247@nvidia.com>

On Wed, Feb 10, 2021 at 09:47:42AM -0400, Jason Gunthorpe wrote:
> On Wed, Feb 10, 2021 at 09:11:49PM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the rdma tree, today's linux-next build (htmldocs) produced
> > this warning:
> > 
> > drivers/infiniband/core/device.c:859: warning: Function parameter or member 'dev' not described in 'ib_port_immutable_read'
> > drivers/infiniband/core/device.c:859: warning: Function parameter or member 'port' not described in 'ib_port_immutable_read'
> > 
> > Introduced by commit
> > 
> >   7416790e2245 ("RDMA/core: Introduce and use API to read port immutable data")
> 
> drivers/infinband is W=1 clean right now in linux-next
> 
> But how can I build *only* drivers/infiniband using W=1 so I can keep
> it that way?
> 
> The rest of the kernel is not clean and creates too much warning noise
> to be usable, even with my mini config.
> 
> Just doing a 'make W=1 drivers/infiniband' is sort of OK, but then I
> end up compiling things twice
> 
> Does anyone know a good solution?
> 
> Jason
> 

Hi Jason,

There was at one point an effort from Andrew Lunn to allow subsystems to
opt in W=1 unconditionally but Masahiro had some concerns with both
approaches:

https://lore.kernel.org/r/20200919190258.3673246-1-andrew@lunn.ch/
https://lore.kernel.org/r/20201001011232.4050282-1-andrew@lunn.ch/

It looks like btrfs has just opted to copy the W=1 flags into its
Makefile:

https://git.kernel.org/next/linux-next/c/3a7b58d632b24ec3321f1ee3027bd407e09e515e

Cheers,
Nathan

  reply	other threads:[~2021-02-10 17:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 10:11 linux-next: build warning after merge of the rdma tree Stephen Rothwell
2021-02-10 13:47 ` Jason Gunthorpe
2021-02-10 17:17   ` Nathan Chancellor [this message]
2021-02-10 22:08   ` Lee Jones
  -- strict thread matches above, loose matches on Subject: below --
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-26  0:55 Stephen Rothwell
2018-07-26  3:05 ` Jason Gunthorpe
2018-07-26  5:10   ` Bart Van Assche
2018-07-26 17:38     ` Jason Gunthorpe
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=20210210171722.GA1670976@ubuntu-m3-large-x86 \
    --to=nathan@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=lee.jones@linaro.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=parav@nvidia.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