From: Boris Brezillon <boris.brezillon@collabora.com>
To: dregan <dregan@broadcom.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Boris Brezillon <bbrezillon@kernel.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH 1/1] mtd: rawnand: Add deassert_wp comment
Date: Fri, 1 Dec 2023 19:38:34 +0100 [thread overview]
Message-ID: <20231201193834.5da80273@collabora.com> (raw)
In-Reply-To: <20231201181542.421077-1-dregan@broadcom.com>
On Fri, 1 Dec 2023 10:15:42 -0800
dregan <dregan@broadcom.com> wrote:
> From: Boris Brezillon <bbrezillon@kernel.org>
I'm pretty sure I shouldn't be the author. The original patch might
have been partly written by me, but this is a fixup on top of it.
>
> Add deassert_wp description comment
>
> Signed-off-by: Boris Brezillon <bbrezillon@kernel.org>
and you should drop my SoB too.
> Signed-off-by: David Regan <dregan@broadcom.com>
> ---
> include/linux/mtd/rawnand.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/mtd/rawnand.h b/include/linux/mtd/rawnand.h
> index fcad94aa0515..3049b05d8a20 100644
> --- a/include/linux/mtd/rawnand.h
> +++ b/include/linux/mtd/rawnand.h
> @@ -1001,6 +1001,8 @@ struct nand_op_parser {
> /**
> * struct nand_operation - NAND operation descriptor
> * @cs: the CS line to select for this NAND operation
> + * @deassert_wp: set to true when the operation requires the WP pin to be
> + * de-asserted (ERASE, PROG, ...)
> * @instrs: array of instructions to execute
> * @ninstrs: length of the @instrs array
> *
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-12-01 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 18:15 [PATCH 1/1] mtd: rawnand: Add deassert_wp comment dregan
2023-12-01 18:38 ` Boris Brezillon [this message]
2023-12-01 18:45 ` David Regan
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=20231201193834.5da80273@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=bbrezillon@kernel.org \
--cc=dregan@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
--cc=vigneshr@ti.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