From: Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>
To: Brian Norris <norris@broadcom.com>
Cc: Sneha Narnakaje <nsnehaprabha@ti.com>,
Artem Bityutskiy <dedekind1@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Deprecate ECCGETLAYOUT
Date: Mon, 23 Aug 2010 13:12:13 +0900 [thread overview]
Message-ID: <4C71F51D.2000600@renesas.com> (raw)
In-Reply-To: <4C6E9C23.6060703@broadcom.com>
On 8/21/2010 12:15 AM, Brian Norris wrote:
[ ... ]
> So this leaves the important patch set as the following two independent,
> slightly different approaches to the same problem; we should choose
> between them:
> [PATCH v3 1/2] mtd: Expand...
> [PATCH v2 2/2] mtd: nand: Expand...
>
> Sorry if my naming, numbering, and failure of intelligence in sending
> e-mail confused anyone. I can resend with distinct names and correct
> numbering if requested.
Thanks for the explanation, got it. I'm following that thread and
already know what's discussed and proposed, but couldn't follow the
changes made between numbered / revised patches with similar subjects.
--
Shinya Kuribayashi
Renesas Electronics
next prev parent reply other threads:[~2010-08-23 4:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 17:53 NAND ECC Layout, sysfs question Brian Norris
2010-08-05 18:18 ` Artem Bityutskiy
2010-08-07 0:11 ` [PATCH] mtd: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT Brian Norris
2010-08-18 18:06 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Brian Norris
2010-08-18 20:37 ` [PATCH v3 1/2] mtd: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT Brian Norris
2010-08-20 0:50 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Shinya Kuribayashi
2010-08-20 15:15 ` Brian Norris
2010-08-23 4:12 ` Shinya Kuribayashi [this message]
2010-08-24 10:45 ` Artem Bityutskiy
2010-08-25 1:12 ` [PATCH v4] mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT Brian Norris
2010-08-30 10:20 ` Artem Bityutskiy
2010-09-18 17:24 ` Artem Bityutskiy
2010-09-18 20:03 ` Brian Norris
2010-09-19 7:17 ` Artem Bityutskiy
2010-09-20 6:28 ` Brian Norris
2010-09-20 6:57 ` [PATCH] mtd: Edit comments on deprecation of " Brian Norris
2010-09-20 8:49 ` Artem Bityutskiy
2010-09-20 7:52 ` [PATCH v4] mtd: nand: Expand nand_ecc_layout, deprecate " Artem Bityutskiy
2010-08-24 10:42 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Artem Bityutskiy
2010-08-18 18:06 ` [PATCH v2 1/2] mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT Brian Norris
2010-08-18 18:06 ` [PATCH v2 2/2] " Brian Norris
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=4C71F51D.2000600@renesas.com \
--to=shinya.kuribayashi.px@renesas.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=norris@broadcom.com \
--cc=nsnehaprabha@ti.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).