From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mike Dunn <mikedunn@newsguy.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH v4 00/10] mtd: nand: rework nand_ecc_ctrl interface for OOB
Date: Fri, 04 May 2012 10:23:57 +0300 [thread overview]
Message-ID: <1336116237.30168.22.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4FA2BC40.70504@newsguy.com>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On Thu, 2012-05-03 at 10:11 -0700, Mike Dunn wrote:
> On 05/03/2012 03:00 AM, Artem Bityutskiy wrote:
> > On Wed, 2012-05-02 at 10:14 -0700, Brian Norris wrote:
> >> Hello,
> >>
> >> This is the fourth version of my patches to change the nand_chip and
> >> nand_ecc_ctrl interfaces so that the nand_ecc_ctrl functions have information
> >> about whether the higher layers actually need OOB data to be read/written
> >> from/to the NAND device.
> >
> > Pushed patches 1,2,6,7,8,9 to l2-mtd.git, thanks!
> >
>
>
> I compile-tested these patches on all arches. No warnings or errors on the
> files that were touched.
I think the worry is that we do not know the specifics of the drivers
and we may break them, while there is no harm if we do not touch them.
So we wanted to only push those patches which were acked.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-04 7:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 17:14 [PATCH v4 00/10] mtd: nand: rework nand_ecc_ctrl interface for OOB Brian Norris
2012-05-02 17:14 ` [PATCH v4 01/10] mtd: nand: add 'oob_required' argument to NAND {read, write}_page interfaces Brian Norris
2012-05-03 17:16 ` Mike Dunn
2012-05-03 17:43 ` Shmulik Ladkani
2012-05-03 22:34 ` Brian Norris
2012-05-04 7:58 ` Artem Bityutskiy
2012-05-02 17:14 ` [PATCH v4 02/10] mtd: nand: pass proper 'oob_required' parameter Brian Norris
2012-05-02 17:14 ` [PATCH v4 03/10] mtd: Blackfin NFC: utilize oob_required parameter Brian Norris
2012-05-03 9:55 ` Artem Bityutskiy
2012-05-02 17:14 ` [PATCH v4 04/10] mtd: cafe_nand: " Brian Norris
2012-05-02 17:14 ` [PATCH v4 05/10] mtd: denali: " Brian Norris
2012-05-02 17:15 ` [PATCH v4 06/10] mtd: eLBC NAND: " Brian Norris
2012-05-02 17:15 ` [PATCH v4 07/10] mtd: IFC " Brian Norris
2012-05-02 17:15 ` [PATCH v4 08/10] mtd: gpmi-nand: utilize oob_requested parameter Brian Norris
2012-05-02 17:15 ` [PATCH v4 09/10] mtd: nand: utilize oob_required parameter Brian Norris
2012-05-02 17:15 ` [PATCH v4 10/10] mtd: pxa3xx_nand: " Brian Norris
2012-05-03 10:00 ` [PATCH v4 00/10] mtd: nand: rework nand_ecc_ctrl interface for OOB Artem Bityutskiy
2012-05-03 17:11 ` Mike Dunn
2012-05-04 7:23 ` Artem Bityutskiy [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=1336116237.30168.22.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mikedunn@newsguy.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).