From: Ivan Djelic <ivan.djelic@parrot.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>, "afzal@ti.com" <afzal@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v3] ARM: OMAP3: gpmc: add BCH ecc api and modes
Date: Thu, 10 May 2012 17:17:25 +0200 [thread overview]
Message-ID: <20120510151725.GA11107@parrot.com> (raw)
In-Reply-To: <1336655257.2625.8.camel@sauron.fi.intel.com>
On Thu, May 10, 2012 at 02:07:37PM +0100, Artem Bityutskiy wrote:
> On Wed, 2012-05-09 at 08:31 -0700, Tony Lindgren wrote:
> > > Note that I could prepare a new MTD patch with BCH ecc code included,
> > > allowing to drop the GPMC BCH ecc api.
> >
> > OK, let's do that then. I'll drop this patch and you can coordinate
> > your patch with Afzal.
>
> Ivan, so are you going to send new patches early enough to make them hit
> 3.5? Can you please then re-send all the dependent patches again and
> again describe what depends on what, because I am getting lost :-)
Yes, I agree this has become a bit confusing. I currently have 2 pending patches:
[1] ARM-OMAP3-gpmc-add-BCH-ecc-api-and-modes_v3.patch (linux-omap)
[2] mtd-nand-omap-add-support-for-hardware-BCH-ecc_v2.patch (linux-mtd)
They should both be dropped. I will basically merge the two patches and
submit a new single patch on MTD only, with no dependency. I won't need
to patch arch/arm/mach-omap2 anymore.
But in order to do so, I need the changes that Afzal has submitted
(in particular [3]). Those changes (and as a consequence, my new patch)
won't hit 3.5.
So, when Afzal's patches are pushed, I'll submit a new, single MTD patch.
BR,
--
Ivan
[1] http://lists.infradead.org/pipermail/linux-mtd/2012-April/040965.html
[2] http://lists.infradead.org/pipermail/linux-mtd/2012-April/041020.html
[3] http://lists.infradead.org/pipermail/linux-mtd/2012-May/041105.html
next prev parent reply other threads:[~2012-05-10 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 12:17 [PATCH v3] ARM: OMAP3: gpmc: add BCH ecc api and modes Ivan Djelic
2012-05-09 0:29 ` Tony Lindgren
2012-05-09 8:07 ` Ivan Djelic
2012-05-09 8:10 ` Ivan Djelic
2012-05-09 15:31 ` Tony Lindgren
2012-05-10 6:49 ` Mohammed, Afzal
2012-05-10 13:07 ` Artem Bityutskiy
2012-05-10 15:17 ` Ivan Djelic [this message]
2012-05-10 15:52 ` Artem Bityutskiy
2012-05-10 17:45 ` Ivan Djelic
2012-05-10 19:02 ` Tony Lindgren
2012-05-11 15:38 ` Artem Bityutskiy
2012-05-11 15:50 ` Mohammed, Afzal
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=20120510151725.GA11107@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=afzal@ti.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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