From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
linux-mtd@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: Fix a kdoc comment
Date: Tue, 18 Mar 2025 17:23:37 +0100 [thread overview]
Message-ID: <87y0x25muu.fsf@bootlin.com> (raw)
In-Reply-To: <174231458436.979692.11846172650554767394.b4-ty@bootlin.com> (Miquel Raynal's message of "Tue, 18 Mar 2025 17:17:09 +0100")
On 18/03/2025 at 17:17:09 +01, Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> On Wed, 05 Mar 2025 20:49:55 +0100, Miquel Raynal wrote:
>> The max_bad_eraseblocks_per_lun member of nand_device obviously
>> describes a number of *maximum* number of bad eraseblocks per LUN.
>>
>> Fix this obvious typo.
>>
>>
>
> Applied to nand/next after fixing the Cc stable line as advised by
> Turod, thanks!
Tudor*, sorry for the typo (:
>
> [1/1] mtd: nand: Fix a kdoc comment
> commit: ca8cbbb2be8f906d9602a6e4324f8adf279e9cc2
>
> Kind regards,
> Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
linux-mtd@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: Fix a kdoc comment
Date: Tue, 18 Mar 2025 17:23:37 +0100 [thread overview]
Message-ID: <87y0x25muu.fsf@bootlin.com> (raw)
In-Reply-To: <174231458436.979692.11846172650554767394.b4-ty@bootlin.com> (Miquel Raynal's message of "Tue, 18 Mar 2025 17:17:09 +0100")
On 18/03/2025 at 17:17:09 +01, Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> On Wed, 05 Mar 2025 20:49:55 +0100, Miquel Raynal wrote:
>> The max_bad_eraseblocks_per_lun member of nand_device obviously
>> describes a number of *maximum* number of bad eraseblocks per LUN.
>>
>> Fix this obvious typo.
>>
>>
>
> Applied to nand/next after fixing the Cc stable line as advised by
> Turod, thanks!
Tudor*, sorry for the typo (:
>
> [1/1] mtd: nand: Fix a kdoc comment
> commit: ca8cbbb2be8f906d9602a6e4324f8adf279e9cc2
>
> Kind regards,
> Miquèl
next prev parent reply other threads:[~2025-03-18 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 19:49 [PATCH] mtd: nand: Fix a kdoc comment Miquel Raynal
2025-03-05 19:49 ` Miquel Raynal
2025-03-06 9:10 ` Tudor Ambarus
2025-03-06 9:10 ` Tudor Ambarus
2025-03-18 16:17 ` Miquel Raynal
2025-03-18 16:17 ` Miquel Raynal
2025-03-18 16:23 ` Miquel Raynal [this message]
2025-03-18 16:23 ` 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=87y0x25muu.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tudor.ambarus@linaro.org \
--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 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.