public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>
Cc: 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 spi-fixes tree
Date: Fri, 18 Mar 2022 18:28:55 +1100	[thread overview]
Message-ID: <20220318182855.301fd666@canb.auug.org.au> (raw)
In-Reply-To: <20220120142103.6a72ec62@canb.auug.org.au>

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

Hi all,

On Thu, 20 Jan 2022 14:21:03 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
> 
> On Fri, 15 Oct 2021 21:14:23 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > 
> > After merging the spi-fixes tree, today's linux-next build (htmldocs)
> > produced this warning:
> > 
> > include/linux/spi/spi.h:671: warning: Function parameter or member 'add_lock' not described in 'spi_controller'
> > 
> > Introduced by commit
> > 
> >   6098475d4cb4 ("spi: Fix deadlock when adding SPI controllers on SPI buses")  
> 
> I am still getting this warning.

I am still getting this warning.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2022-03-18  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 10:14 linux-next: build warning after merge of the spi-fixes tree Stephen Rothwell
2022-01-20  3:21 ` Stephen Rothwell
2022-03-18  7:28   ` Stephen Rothwell [this message]
2022-04-04  3:28     ` 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=20220318182855.301fd666@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=broonie@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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