From: Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>
To: Brian Norris <norris@broadcom.com>
Cc: linux-mtd@lists.infradead.org,
Sneha Narnakaje <nsnehaprabha@ti.com>,
David Woodhouse <dwmw2@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH v2 0/2] Deprecate ECCGETLAYOUT
Date: Fri, 20 Aug 2010 09:50:56 +0900 [thread overview]
Message-ID: <4C6DD170.1060807@renesas.com> (raw)
In-Reply-To: <1282154806-9420-1-git-send-email-norris@broadcom.com>
Hi,
[PATCH] mtd: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
[PATCH v2 0/2] Deprecate ECCGETLAYOUT
[PATCH v2 1/2] mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
[PATCH v2 2/2] mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
[PATCH v3 1/2] mtd: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
[PATCH v3 2/2] (I can't find this in my inbox, by the way)
I'd like to see the info about what's updated in v2, v3 when revised.
By the way.
On 8/19/2010 3:06 AM, Brian Norris wrote:
> Brian Norris (2):
> mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
> mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
Two patches with the same title. Similar symptom can be seen in your
latest v3 post (we can't find [PATCH v3 2/2]). Perhaps something weird
is in your repository (or git settings).
--
Shinya Kuribayashi
Renesas Electronics
next prev parent reply other threads:[~2010-08-20 0:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C5CA4A1.1040000@broadcom.com>
2010-08-18 18:06 ` 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 ` Shinya Kuribayashi [this message]
2010-08-20 15:15 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Brian Norris
2010-08-23 4:12 ` Shinya Kuribayashi
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=4C6DD170.1060807@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
Powered by JetHome