From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v7 1/2] mtd: nand: davinci: add support for on-die ECC engine type
Date: Fri, 15 Nov 2024 20:48:09 +0100 [thread overview]
Message-ID: <871pzcnurq.fsf@bootlin.com> (raw)
In-Reply-To: <ZzcL53TmSOwTuIFM@gmail.com> (Marcus Folkesson's message of "Fri, 15 Nov 2024 09:52:55 +0100")
On 15/11/2024 at 09:52:55 +01, Marcus Folkesson <marcus.folkesson@gmail.com> wrote:
> On Thu, Nov 07, 2024 at 02:47:07PM +0100, Marcus Folkesson wrote:
>> Some chips, e.g. Micron MT29F1G08ABBFAH4, has a mandatory on-die ECC.
>> Add "on-die" as ECC engine type in order to be compatible with those.
>>
>> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
>> ---
>
> Can someone please take a look at this patch?
Well, it's v7, so I believe we've given attention to this
patchset :-) Also, please consider 2 weeks as a better delay for pings.
It is flagged "okay" on my side, but will only be applied after -rc1
unless I get negative feedback about it in the mean time.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-11-15 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 13:47 [PATCH v7 0/2] Add support for "on-die" ECC on Davinci Marcus Folkesson
2024-11-07 13:47 ` [PATCH v7 1/2] mtd: nand: davinci: add support for on-die ECC engine type Marcus Folkesson
2024-11-15 8:52 ` Marcus Folkesson
2024-11-15 19:48 ` Miquel Raynal [this message]
2024-11-07 13:47 ` [PATCH v7 2/2] dt-bindings: mtd: davinci: convert to yaml Marcus Folkesson
2024-11-07 18:00 ` Conor Dooley
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=871pzcnurq.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marcus.folkesson@gmail.com \
--cc=richard@nod.at \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).