From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] mtd: nand: export nand_get_flash_type function
Date: Sun, 14 Jan 2018 19:22:33 +0100 [thread overview]
Message-ID: <1515954153.8426.7.camel@embedded.rocks> (raw)
In-Reply-To: <CAOMZO5Ca9XM+12rPxTadb7LgHJz_xP9A=bg5azKbbMGDkUoLKQ@mail.gmail.com>
On Sun, 2018-01-14 at 15:55 -0200, Fabio Estevam wrote:
> Hi Jörg,
>
> On Sun, Jan 14, 2018 at 2:14 PM, Jörg Krause
> <joerg.krause@embedded.rocks> wrote:
> > `nand_get_flash_type()` allows identification of supported NAND flashs.
> > The function is useful in SPL (like mxs_nand_spl.c) to lookup for a NAND
> > flash (which does not support ONFi) instead of using nand_simple.c and
> > hard-coding all required NAND parameters.
> >
> > Signed-off-by: Jörg Krause <joerg.krause@embedded.rocks>
>
> Thanks for your series.
>
> You missed to add the U-Boot NAND maintainer (Scott Wood).
>
> Please resend the series with him on Cc.
Thanks, will do! I missed him because the custodian git repos last
change is from 2016.
Jörg
next prev parent reply other threads:[~2018-01-14 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 16:14 [U-Boot] [PATCH 0/4] Add CONFIG_SPL_NAND_IDENT Jörg Krause
2018-01-14 16:14 ` [U-Boot] [PATCH 1/4] mtd: nand: export nand_get_flash_type function Jörg Krause
2018-01-14 17:55 ` Fabio Estevam
2018-01-14 18:22 ` Jörg Krause [this message]
2018-01-14 16:14 ` [U-Boot] [PATCH 2/4] spl, nand: add option CONFIG_SPL_NAND_IDENT to lookup for supported NAND chips Jörg Krause
2018-01-14 16:14 ` [U-Boot] [PATCH 3/4] mtd: nand: mxs_nand_spl: refactor mxs_flash_ident Jörg Krause
2018-01-14 16:14 ` [U-Boot] [PATCH 4/4] mtd: nand: mxs_nand_spl: add mxs_flash_full_ident Jörg Krause
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=1515954153.8426.7.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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 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.