From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Dirk Hörner" <dirker@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: MTD NAND updates
Date: Thu, 31 May 2012 19:01:21 +0200 [thread overview]
Message-ID: <20120531170121.GQ30400@pengutronix.de> (raw)
In-Reply-To: <CAOoHCj8GbWPQRoPq8+dCnrOS-_gttcKa_VOEup-7noOKL-Ljyg@mail.gmail.com>
Hi Dirk,
On Thu, May 31, 2012 at 06:31:20PM +0200, Dirk Hörner wrote:
> Hi List,
>
> while going through the NAND specific parts of the MTD layer I noticed that
> there are quite a few updates available from recent Linux kernel versions:
> * detection of flashes via ONFI
> * improved detection of flashes via extid
> * added device id's in the hard-coded table
>
> I'd like to provide some patches, just a few questions:
> * should I base them on master or next?
master is fine. I'll handle the conflicts if necessary.
> * should I try to cherry-pick updates from the kernel or should I just
> merge stuff from the kernel and send patches split into logical parts
> (onfi, extid, id additions)?
Splitting into logical parts seems to make the most sense. If it's just
a single patch you can also cherry-pick it, but we don't need the whole
feature-add-then-several-bugfixes history.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-05-31 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 16:31 Dirk Hörner
2012-05-31 17:01 ` Sascha Hauer [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=20120531170121.GQ30400@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=dirker@gmail.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