public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Benedikt Spranger <b.spranger@linutronix.de>
To: Eugen Hristev <eugen.hristev@linaro.org>
Cc: John Ogness <john.ogness@linutronix.de>, u-boot@lists.denx.de
Subject: Re: [PATCH 4/5] mtd: nand: Update NAND manufacturer Ids
Date: Tue, 12 Nov 2024 14:57:45 +0100	[thread overview]
Message-ID: <20241112145745.72d14afc@mitra> (raw)
In-Reply-To: <56e48bdf-0dd0-469a-9acb-7c5b75c1a48e@linaro.org>

On Tue, 12 Nov 2024 15:39:23 +0200
Eugen Hristev <eugen.hristev@linaro.org> wrote:

Hi Eugen,
> On 10/18/24 11:30, Benedikt Spranger wrote:
> > Align manufacturer Ids with the Id list from Linux kernel v6.11.
> > While at it, sort the entries in alphabetical order.
> > 
> > Signed-off-by: Benedikt Spranger <b.spranger@linutronix.de>
> > Reviewed-by: John Ogness <john.ogness@linutronix.de>
> > ---
> >  drivers/mtd/nand/raw/nand_ids.c | 22 ++++++++++++----------
> >  include/linux/mtd/rawnand.h     | 23 +++++++++++++----------
> >  2 files changed, 25 insertions(+), 20 deletions(-)
> > 
> > diff --git a/drivers/mtd/nand/raw/nand_ids.c b/drivers/mtd/nand/raw/nand_ids.c
> > index 4f46378ffe1..e40facf774c 100644
> > --- a/drivers/mtd/nand/raw/nand_ids.c
> > +++ b/drivers/mtd/nand/raw/nand_ids.c
> > @@ -180,20 +180,22 @@ struct nand_flash_dev nand_flash_ids[] = {
> >  
> >  /* Manufacturer IDs */
> >  struct nand_manufacturer nand_manuf_ids[] = {
> > -	{NAND_MFR_TOSHIBA, "Toshiba", &toshiba_nand_manuf_ops},
> > -	{NAND_MFR_SAMSUNG, "Samsung", &samsung_nand_manuf_ops},
> > +	{NAND_MFR_AMD, "AMD/Spansion", &amd_nand_manuf_ops},
> > +	{NAND_MFR_ATO, "ATO"},
> > +	{NAND_MFR_EON, "Eon"},
> > +	{NAND_MFR_EON, "ESMT"},
> 
> Did you mean NAND_MFR_ESMT here ?
Yes, fatfingered that...

Regards
    Benedikt Spranger

  reply	other threads:[~2024-11-12 13:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  8:30 [PATCH 0/5] collected fallout of porting an ATSAMA5D27 based board Benedikt Spranger
2024-10-18  8:30 ` [PATCH 0/5] collected fallout of porting an ATSAMA5D2 " Benedikt Spranger
2024-11-12 13:45   ` Eugen Hristev
2024-11-19 15:46     ` Eugen Hristev
2024-11-21 22:48       ` Michael Nazzareno Trimarchi
2024-10-18  8:30 ` [PATCH 1/5] tiny-printf: Handle NULL pointer argument to %s Benedikt Spranger
2024-10-18  8:30 ` [PATCH 2/5] drivers/mtd/ubispl/ubispl.c: Fix error message Benedikt Spranger
2024-10-18  8:30 ` [PATCH 3/5] mtd: nand: raw: Fix potential NULL pointer dereference Benedikt Spranger
2024-10-18  8:30 ` [PATCH 4/5] mtd: nand: Update NAND manufacturer Ids Benedikt Spranger
2024-11-12 13:39   ` Eugen Hristev
2024-11-12 13:57     ` Benedikt Spranger [this message]
2024-11-12 14:48       ` Eugen Hristev
2024-10-18  8:30 ` [PATCH 5/5] mtd: nand: raw: atmel_nand: Add missing nand_scan_ident() Benedikt Spranger
2024-10-18 13:11 ` [PATCH 0/5] collected fallout of porting an ATSAMA5D27 based board Alexander Dahl
2024-10-18 14:19   ` Benedikt Spranger
2024-10-21  6:03     ` Alexander Dahl
2024-10-21  7:17       ` Eugen Hristev
2024-10-21  7:36         ` Alexander Dahl
2024-10-21 12:49           ` Eugen Hristev
2024-10-21 12:30         ` Benedikt Spranger
2024-10-21 12:47           ` Eugen Hristev
2024-10-21 10:20       ` Benedikt Spranger
2024-10-21 10:51         ` Alexander Dahl

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=20241112145745.72d14afc@mitra \
    --to=b.spranger@linutronix.de \
    --cc=eugen.hristev@linaro.org \
    --cc=john.ogness@linutronix.de \
    --cc=u-boot@lists.denx.de \
    /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