From: Tony Lindgren <tony@atomide.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: "artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
Ivan Djelic <ivan.djelic@parrot.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 0/3] GPMC NAND isr using standard API
Date: Tue, 22 May 2012 09:44:15 -0700 [thread overview]
Message-ID: <20120522164413.GF16308@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E98F0E1@DBDE01.ent.ti.com>
* Mohammed, Afzal <afzal@ti.com> [120522 00:05]:
> Hi Artem,
>
> On Tue, May 22, 2012 at 11:44:43, Artem Bityutskiy wrote:
> > You merge the 2 trees and work on top of that? Or you wait for 3.5-r1
> > when everything is merged and work on top of that?
>
> I will merge 2 trees & do
>
> Tony, are you ok with that ?
I suggest you guys do your own merge of the two trees until -rc1
is out, then start using -rc1 as the base like Artem suggested.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: "artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
Ivan Djelic <ivan.djelic@parrot.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 0/3] GPMC NAND isr using standard API
Date: Tue, 22 May 2012 09:44:15 -0700 [thread overview]
Message-ID: <20120522164413.GF16308@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E98F0E1@DBDE01.ent.ti.com>
* Mohammed, Afzal <afzal@ti.com> [120522 00:05]:
> Hi Artem,
>
> On Tue, May 22, 2012 at 11:44:43, Artem Bityutskiy wrote:
> > You merge the 2 trees and work on top of that? Or you wait for 3.5-r1
> > when everything is merged and work on top of that?
>
> I will merge 2 trees & do
>
> Tony, are you ok with that ?
I suggest you guys do your own merge of the two trees until -rc1
is out, then start using -rc1 as the base like Artem suggested.
Regards,
Tony
next prev parent reply other threads:[~2012-05-22 16:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 14:38 [PATCH 0/3] GPMC NAND isr using standard API Afzal Mohammed
2012-05-15 14:38 ` Afzal Mohammed
2012-05-15 14:38 ` [PATCH 1/3] ARM: OMAP2+: gpmc: Modify interrupt handling Afzal Mohammed
2012-05-15 14:38 ` Afzal Mohammed
2012-05-15 15:06 ` Mohammed, Afzal
2012-05-15 14:38 ` [PATCH 2/3] ARM: OMAP2+: gpmc-nand: Modify Interrupt handling Afzal Mohammed
2012-05-15 14:38 ` Afzal Mohammed
2012-05-15 14:38 ` [PATCH 3/3] mtd: nand: omap2: use gpmc provided irqs Afzal Mohammed
2012-05-15 14:38 ` Afzal Mohammed
2012-05-19 12:50 ` [PATCH 0/3] GPMC NAND isr using standard API Ivan Djelic
2012-05-19 12:50 ` Ivan Djelic
2012-05-22 4:26 ` Mohammed, Afzal
2012-05-22 4:26 ` Mohammed, Afzal
2012-05-22 6:14 ` Artem Bityutskiy
2012-05-22 6:14 ` Artem Bityutskiy
2012-05-22 7:01 ` Mohammed, Afzal
2012-05-22 7:01 ` Mohammed, Afzal
2012-05-22 16:44 ` Tony Lindgren [this message]
2012-05-22 16:44 ` Tony Lindgren
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=20120522164413.GF16308@atomide.com \
--to=tony@atomide.com \
--cc=afzal@ti.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dwmw2@infradead.org \
--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 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.