From: "Dirk Hörner" <dirker@gmail.com>
To: barebox@lists.infradead.org
Subject: MTD NAND updates
Date: Thu, 31 May 2012 18:31:20 +0200 [thread overview]
Message-ID: <CAOoHCj8GbWPQRoPq8+dCnrOS-_gttcKa_VOEup-7noOKL-Ljyg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 565 bytes --]
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?
* 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)?
Thanks,
Dirk
[-- Attachment #1.2: Type: text/html, Size: 716 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-05-31 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 16:31 Dirk Hörner [this message]
2012-05-31 17:01 ` Sascha Hauer
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=CAOoHCj8GbWPQRoPq8+dCnrOS-_gttcKa_VOEup-7noOKL-Ljyg@mail.gmail.com \
--to=dirker@gmail.com \
--cc=barebox@lists.infradead.org \
/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