public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ivan Djelic <ivan.djelic@parrot.com>
Cc: "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>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH v3] ARM: OMAP3: gpmc: add BCH ecc api and modes
Date: Thu, 10 May 2012 12:02:43 -0700	[thread overview]
Message-ID: <20120510190243.GM21851@atomide.com> (raw)
In-Reply-To: <20120510174527.GA11275@parrot.com>

* Ivan Djelic <ivan.djelic@parrot.com> [120510 10:49]:
> On Thu, May 10, 2012 at 04:52:18PM +0100, Artem Bityutskiy wrote:
> > On Thu, 2012-05-10 at 17:17 +0200, Ivan Djelic wrote:
> > > 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.
> > 
> > But this is not going to happen this merge window as I understood, may
> > be not even the next one. We need to make UBIFS happy sooner than that,
> > I think. So may be we go forward with your original patch?
> 
> I'm OK with this too, as the patches are ready and tested.
> The MTD patch is [2], it depends on [1] which has been pushed, then dropped by Tony.
> Do you need me to repost [2] ?
> 
> Tony, sorry to backpedal on this: would you re-push patch [1], if indeed Afzal's patches
> are not going to be merged soon ? In the meantime, I can prepare a patch on top of Afzal's to
> have a smooth transition w.r.t BCH support. What do you think ?

Yes this is OK with me as this removes the blocker for UBIFS work.

For arch/arm/mach-omap2/gpmc.c, I have the following two patches
queued:

27aeb3da5f97c55f61d92e3dbfb738762f76dc32 Merge tag 'omap-cleanup-for-v3.5' into tmp-merge
2c65e7440d56b3b285d1c95563b4dcce8e40dea3 GPMC: add ECC control definitions
355f8eee48134ba10ca81664ee90eeb240f5f928 ARM: OMAP2+: GPMC: resolve type-conversion warning from sparse

Looks your patch applies to v3.4-rc6 and what I have queued without
conflicts, so I suggest you merge both via MTD patches:

Acked-by: Tony Lindgren <tony@atomide.com>

 
> [1] http://lists.infradead.org/pipermail/linux-mtd/2012-April/040965.html
> [2] http://lists.infradead.org/pipermail/linux-mtd/2012-April/041020.html

  reply	other threads:[~2012-05-10 19:02 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
2012-05-10 15:52           ` Artem Bityutskiy
2012-05-10 17:45             ` Ivan Djelic
2012-05-10 19:02               ` Tony Lindgren [this message]
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=20120510190243.GM21851@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal@ti.com \
    --cc=dedekind1@gmail.com \
    --cc=ivan.djelic@parrot.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    /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