All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Regan <dregan@broadcom.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Boris Brezillon <bbrezillon@kernel.org>,
	David Regan <dregan@broadcom.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 nand tree
Date: Thu, 30 Nov 2023 21:03:00 -0800	[thread overview]
Message-ID: <CAA_RMS5THkAQxEPWvtpcbb=F-G1xdntZPTmzhAhvK6voWi6VOA@mail.gmail.com> (raw)
In-Reply-To: <20231201125648.71d7586d@canb.auug.org.au>

Hi Stephen,

from this post:
https://github.com/bbrezillon/linux/commit/e612e1f2c69a33ac5f2c91d13669f0f172d58717

Looks like this comment needs to be added:

* @deassert_wp: set to true when the operation requires the WP pin to be
*                         de-asserted (ERASE, PROG, ...)


What's the best way to go about doing this?

Thanks!

-Dave


On Thu, Nov 30, 2023 at 5:56 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the nand tree, today's linux-next build (htmldocs) produced
> this warning:
>
> include/linux/mtd/rawnand.h:1016: warning: Function parameter or member 'deassert_wp' not described in 'nand_operation'
>
> Introduced by commit
>
>   e82a5a014dd5 ("mtd: rawnand: Add destructive operation")
>
> --
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2023-12-01  5:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01  1:56 linux-next: build warning after merge of the nand tree Stephen Rothwell
2023-12-01  5:03 ` David Regan [this message]
2023-12-01 11:55   ` Miquel Raynal
  -- strict thread matches above, loose matches on Subject: below --
2023-01-16  3:32 Stephen Rothwell
2022-02-08  6:00 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='CAA_RMS5THkAQxEPWvtpcbb=F-G1xdntZPTmzhAhvK6voWi6VOA@mail.gmail.com' \
    --to=dregan@broadcom.com \
    --cc=bbrezillon@kernel.org \
    --cc=boris.brezillon@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=miquel.raynal@bootlin.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 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.