From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Dominique Martinet <dominique.martinet@atmark-techno.com>
Cc: Richard Weinberger <richard@nod.at>,
Md Sadre Alam <md.alam@oss.qualcomm.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Daisuke Mizobuchi <mizo@atmark-techno.com>
Subject: Re: [PATCH RFC v2] mtd: spinand: winbond: add support for W25N04LW
Date: Wed, 12 Aug 2026 09:35:55 +0200 [thread overview]
Message-ID: <87tsozn63o.fsf@bootlin.com> (raw)
In-Reply-To: <anv-3hSRMVgJAsOt@atmark-techno.com> (Dominique Martinet's message of "Wed, 12 Aug 2026 14:04:30 +0900")
On 12/08/2026 at 14:04:30 +09, Dominique Martinet <dominique.martinet@atmark-techno.com> wrote:
> Dominique Martinet wrote on Wed, Aug 12, 2026 at 04:14:02AM +0000:
>> + // the W25N04LW chip actually has two free ranges per section:
>> + // "User Data I" at (16 * section) + 4, length 12
>> + // "User Data II" at (16 * section) + 2, length 2
>> + // The later is not ECC protected so this only returns User Data I
>
> (will fix to use block comment like the rest of the file + latter typo
> as per Sashiko comment in v3, after we've reached an agreement on what
> to do here -- there were no other Sashiko comment)
I haven't checked the diff yet, but the commit message contains a SoB
from anther person which is listed first. You must be Author + first SoB or
you can give someone else authorship + first SoB and take 2nd SoB (which
means you carried the patch without changing it). If you want to credit
another person, please have a look at the Co-developed-by wording.
Thanks!
Miquèl
next prev parent reply other threads:[~2026-08-12 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 4:14 [PATCH RFC v2] mtd: spinand: winbond: add support for W25N04LW Dominique Martinet
2026-08-12 5:04 ` Dominique Martinet
2026-08-12 7:35 ` Miquel Raynal [this message]
2026-08-12 8:08 ` Dominique Martinet
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=87tsozn63o.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=dominique.martinet@atmark-techno.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=md.alam@oss.qualcomm.com \
--cc=mizo@atmark-techno.com \
--cc=richard@nod.at \
--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