From: "Brian Norris" <norris@broadcom.com>
To: "Shinya Kuribayashi" <shinya.kuribayashi.px@renesas.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Sneha Narnakaje <nsnehaprabha@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <norris@broadcom.com>
Subject: Re: [PATCH v2 0/2] Deprecate ECCGETLAYOUT
Date: Fri, 20 Aug 2010 08:15:47 -0700 [thread overview]
Message-ID: <4C6E9C23.6060703@broadcom.com> (raw)
In-Reply-To: <4C6DD170.1060807@renesas.com>
Hi,
Sorry for the problems. I will try to explain.
On 08/19/2010 05:50 PM, Shinya Kuribayashi wrote:
> [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)
There was no PATCH v3 2/2. See below.
> I'd like to see the info about what's updated in v2, v3 when revised.
The only difference is that I actually sent the correct patch :) Again,
I explain below.
> 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).
No problem with git, just my inability to express my "2 independent
patch" problem properly.
First, I sent my original patch 08/06/2010:
[PATCH] mtd: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
Realizing this may not necessarily have been the *best* way to
accomplish my goal, I sent v2:
[PATCH v2 1/2] mtd: nand: Expand...
[PATCH v2 2/2] mtd: nand: Expand...
These two patches were supposed to be two different, independent
approaches to the same task; with discussion over how best to do this,
we should settle on one of the two patches. I decided (for good or for
bad) that they didn't need a new title - they were essentially the same
code with a slight twist. However, instead of sending two different
patches, I sent the same one twice (my mistake).
Finally, I sent v3 to include just the missing patch:
[PATCH v3 1/2] mtd: Expand...
I only included the missing patch and called it v3.
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,
Brian
WARNING: multiple messages have this Message-ID (diff)
From: "Brian Norris" <norris@broadcom.com>
To: "Shinya Kuribayashi" <shinya.kuribayashi.px@renesas.com>
Cc: "linux-mtd@lists.infradead.org" <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>,
"Brian Norris" <norris@broadcom.com>
Subject: Re: [PATCH v2 0/2] Deprecate ECCGETLAYOUT
Date: Fri, 20 Aug 2010 08:15:47 -0700 [thread overview]
Message-ID: <4C6E9C23.6060703@broadcom.com> (raw)
In-Reply-To: <4C6DD170.1060807@renesas.com>
Hi,
Sorry for the problems. I will try to explain.
On 08/19/2010 05:50 PM, Shinya Kuribayashi wrote:
> [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)
There was no PATCH v3 2/2. See below.
> I'd like to see the info about what's updated in v2, v3 when revised.
The only difference is that I actually sent the correct patch :) Again,
I explain below.
> 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).
No problem with git, just my inability to express my "2 independent
patch" problem properly.
First, I sent my original patch 08/06/2010:
[PATCH] mtd: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
Realizing this may not necessarily have been the *best* way to
accomplish my goal, I sent v2:
[PATCH v2 1/2] mtd: nand: Expand...
[PATCH v2 2/2] mtd: nand: Expand...
These two patches were supposed to be two different, independent
approaches to the same task; with discussion over how best to do this,
we should settle on one of the two patches. I decided (for good or for
bad) that they didn't need a new title - they were essentially the same
code with a slight twist. However, instead of sending two different
patches, I sent the same one twice (my mistake).
Finally, I sent v3 to include just the missing patch:
[PATCH v3 1/2] mtd: Expand...
I only included the missing patch and called it v3.
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,
Brian
next prev parent reply other threads:[~2010-08-20 15:16 UTC|newest]
Thread overview: 40+ 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-07 0:11 ` Brian Norris
2010-08-18 18:06 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Brian Norris
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-18 20:37 ` Brian Norris
2010-08-20 0:50 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Shinya Kuribayashi
2010-08-20 0:50 ` Shinya Kuribayashi
2010-08-20 15:15 ` Brian Norris [this message]
2010-08-20 15:15 ` Brian Norris
2010-08-23 4:12 ` Shinya Kuribayashi
2010-08-23 4:12 ` Shinya Kuribayashi
2010-08-24 10:45 ` Artem Bityutskiy
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-25 1:12 ` Brian Norris
2010-08-30 10:20 ` Artem Bityutskiy
2010-08-30 10:20 ` Artem Bityutskiy
2010-09-18 17:24 ` Artem Bityutskiy
2010-09-18 17:24 ` Artem Bityutskiy
2010-09-18 20:03 ` Brian Norris
2010-09-18 20:03 ` Brian Norris
2010-09-19 7:17 ` Artem Bityutskiy
2010-09-19 7:17 ` Artem Bityutskiy
2010-09-20 6:28 ` Brian Norris
2010-09-20 6:28 ` Brian Norris
2010-09-20 6:57 ` [PATCH] mtd: Edit comments on deprecation of " Brian Norris
2010-09-20 6:57 ` Brian Norris
2010-09-20 8:49 ` Artem Bityutskiy
2010-09-20 8:49 ` Artem Bityutskiy
2010-09-20 7:52 ` [PATCH v4] mtd: nand: Expand nand_ecc_layout, deprecate " Artem Bityutskiy
2010-09-20 7:52 ` Artem Bityutskiy
2010-08-24 10:42 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Artem Bityutskiy
2010-08-24 10:42 ` 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 ` Brian Norris
2010-08-18 18:06 ` [PATCH v2 2/2] " Brian Norris
2010-08-18 18:06 ` 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=4C6E9C23.6060703@broadcom.com \
--to=norris@broadcom.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nsnehaprabha@ti.com \
--cc=shinya.kuribayashi.px@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.