All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v4-alt 0/6] GPMC driver migrate one
Date: Fri, 11 May 2012 13:00:49 -0700	[thread overview]
Message-ID: <20120511200049.GY21851@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E98A339@DBDE01.ent.ti.com>

* Mohammed, Afzal <afzal@ti.com> [120509 23:39]:
> Hi Tony,
> 
> On Wed, May 09, 2012 at 03:06:26, Tony Lindgren wrote:
> 
> > > To resolve this and as per your earlier question on whether old along
> > > with new interface can be made to work parallely, here is suggestion
> > > from my end to deal with it.
> > 
> > I think this is the only way to keep this all building and booting
> > for each patch in the series, no? If so, then we should select this
> > option. The first patch should be broken up into more readable patches,
> > it seems that you can do that without breaking things.
> 
> Bisectability has been maintained in the patches.
> 
> Ok, I will proceed by keeping old & new interface together, will
> try to achieve it in smaller patches and without hacks.
> 
> > > Please let me know whether you are fine in taking patch series
> > > as in v4 (that converts all boards at once, with further revisions
> > > based on review comments).
> > 
> > It seems that there are still some pending comments and we need to
> > have the hwmod entries merged first by Paul.
> 
> Ok, first I will try to get hwmod in.

Let's try to get merged these into l-o master around -rc2 so we can
have them tested properly for a few weeks before v3.6 merge window.

Regards,

Tony

  reply	other threads:[~2012-05-11 20:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  8:45 [PATCH v4-alt 0/6] GPMC driver migrate one Afzal Mohammed
2012-05-02  8:45 ` [PATCH v4-alt 1/6] ARM: OMAP2+: gpmc: driver conversion Afzal Mohammed
2012-05-02  8:46 ` [PATCH v4-alt 2/6] ARM: OMAP2+: gpmc: Adapt to HWMOD Afzal Mohammed
2012-05-02  8:46 ` [PATCH v4-alt 3/6] ARM: OMAP3: hwmod data: add gpmc Afzal Mohammed
2012-05-06  2:04   ` Paul Walmsley
2012-05-07 11:12     ` Mohammed, Afzal
2012-05-08 13:12       ` Mohammed, Afzal
2012-05-08 15:37         ` Paul Walmsley
2012-05-08 15:32       ` Paul Walmsley
2012-05-10  6:03         ` Mohammed, Afzal
2012-05-12  4:23           ` Mohammed, Afzal
2012-05-22  6:47           ` Paul Walmsley
2012-05-22 11:35             ` Mohammed, Afzal
2012-05-22 16:42             ` Tony Lindgren
2012-05-23 14:51               ` Paul Walmsley
2012-05-25  7:26                 ` Tony Lindgren
2012-05-25 10:15                   ` Mohammed, Afzal
2012-06-05  7:13                     ` Tony Lindgren
2012-06-12 11:36               ` Mohammed, Afzal
2012-05-02  8:46 ` [PATCH v4-alt 4/6] ARM: OMAP2+: gpmc: driver migration hack Afzal Mohammed
2012-05-02  8:46 ` [PATCH v4-alt 5/6] ARM: OMAP2+: gpmc-smsc911x: Add helper for driver conversion Afzal Mohammed
2012-05-02  8:46 ` [PATCH v4-alt 6/6] ARM: OMAP2+: board omap3evm: gpmc driver adaptation Afzal Mohammed
2012-05-08 21:36 ` [PATCH v4-alt 0/6] GPMC driver migrate one Tony Lindgren
2012-05-10  6:35   ` Mohammed, Afzal
2012-05-11 20:00     ` Tony Lindgren [this message]
2012-05-14  4:59       ` 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=20120511200049.GY21851@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal@ti.com \
    --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 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.