public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Santhosh Kumar K <s-k6@ti.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: <richard@nod.at>, <vigneshr@ti.com>, <quic_sridsn@quicinc.com>,
	<quic_mdalam@quicinc.com>, <linux-mtd@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <p-mantena@ti.com>, <s-k6@ti.com>
Subject: Re: [PATCH 3/3] mtd: spinand: winbond: Fix oob_layout for W25N01JW
Date: Mon, 27 Jan 2025 12:18:33 +0530	[thread overview]
Message-ID: <ff477be2-0ee3-400e-9cbb-316d63f31d21@ti.com> (raw)
In-Reply-To: <87r053lwg1.fsf@bootlin.com>

Hello, Miquel,

On 16/01/25 00:46, Miquel Raynal wrote:
> Hello Santhosh,
> 
> On 02/01/2025 at 17:21:10 +0530, Santhosh Kumar K <s-k6@ti.com> wrote:
> 
>> Fix the W25N01JW's oob_layout according to the datasheet. [1]
>>
>> [1] https://www.winbond.com/hq/product/code-storage-flash-memory/qspinand-flash/?__locale=en&partNo=W25N01JW
>>
>> Fixes: 6a804fb72de5 ("mtd: spinand: winbond: add support for serial NAND flash")
>> CC: Sridharan S N <quic_sridsn@quicinc.com>
>> Signed-off-by: Santhosh Kumar K <s-k6@ti.com>
> 
> There have been changes in this driver, I'd suggest to rebase your work
> once -rc1 is out.
> 
> Also, Please add Cc: stable in copy and either move this patch first in
> the series, or even detach it because it has little to do with the two
> other patches.

Got it, I'll detach this one.

Regards,
Santhosh.

> 
> Thanks!
> Miquèl

      reply	other threads:[~2025-01-27  6:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 11:51 [PATCH 0/3] Add OSPI NAND support Santhosh Kumar K
2025-01-02 11:51 ` [PATCH 1/3] mtd: spinand: Define OctalIO ops Santhosh Kumar K
2025-01-15 19:19   ` Miquel Raynal
2025-01-27  6:48     ` Santhosh Kumar K
2025-01-02 11:51 ` [PATCH 2/3] mtd: spinand: winbond: Add support for W35N01JW Santhosh Kumar K
2025-01-02 11:51 ` [PATCH 3/3] mtd: spinand: winbond: Fix oob_layout for W25N01JW Santhosh Kumar K
2025-01-15 19:16   ` Miquel Raynal
2025-01-27  6:48     ` Santhosh Kumar K [this message]

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=ff477be2-0ee3-400e-9cbb-316d63f31d21@ti.com \
    --to=s-k6@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=p-mantena@ti.com \
    --cc=quic_mdalam@quicinc.com \
    --cc=quic_sridsn@quicinc.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