From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Boris Brezillon <boris.brezillon@collabora.com>
Cc: Sean Nyekjaer <sean@geanix.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the nand tree
Date: Tue, 8 Feb 2022 17:00:56 +1100 [thread overview]
Message-ID: <20220208170056.0054db04@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
Hi all,
After merging the nand tree, today's linux-next build (htmldocs) produced
this warning:
include/linux/mtd/rawnand.h:1307: warning: Function parameter or member 'resume_wq' not described in 'nand_chip'
Introduced by commit
0ff4eb01ffb9 ("mtd: rawnand: protect access to rawnand devices while in suspend")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-02-08 6:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 6:00 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-01 1:56 linux-next: build warning after merge of the nand tree Stephen Rothwell
2023-12-01 5:03 ` David Regan
2023-12-01 11:55 ` Miquel Raynal
2023-01-16 3:32 Stephen Rothwell
2020-11-20 0:39 Stephen Rothwell
2020-11-20 11:23 ` Miquel Raynal
2020-11-20 12:01 ` Boris Brezillon
2020-11-20 12:58 ` Serge Semin
2020-11-20 13:01 ` Serge Semin
2020-11-03 6:37 Stephen Rothwell
2020-11-06 4:31 ` Stephen Rothwell
2020-09-14 1:40 Stephen Rothwell
2020-03-11 2:06 Stephen Rothwell
2019-04-02 23:22 Stephen Rothwell
2019-04-03 7:49 ` Miquel Raynal
2018-10-08 0:38 Stephen Rothwell
2018-10-08 7:53 ` Miquel Raynal
2018-10-08 11:06 ` Stephen Rothwell
2018-07-19 2:28 Stephen Rothwell
2018-07-09 1:51 Stephen Rothwell
2018-07-09 6:16 ` Boris Brezillon
2018-07-09 6:51 ` Miquel Raynal
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=20220208170056.0054db04@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=boris.brezillon@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=sean@geanix.com \
/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).