From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: Ivan Djelic <ivan.djelic@parrot.com>,
"tony@atomide.com" <tony@atomide.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:14:43 +0300 [thread overview]
Message-ID: <1337667283.2483.83.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E98EE28@DBDE01.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 322 bytes --]
On Tue, 2012-05-22 at 04:26 +0000, Mohammed, Afzal wrote:
> Tony, Artem, how should the conflict between omap & mtd trees be handled
> for patch series ?
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?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-22 6:11 UTC|newest]
Thread overview: 10+ 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 ` [PATCH 1/3] ARM: OMAP2+: gpmc: Modify interrupt handling 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 ` [PATCH 3/3] mtd: nand: omap2: use gpmc provided irqs Afzal Mohammed
2012-05-19 12:50 ` [PATCH 0/3] GPMC NAND isr using standard API Ivan Djelic
2012-05-22 4:26 ` Mohammed, Afzal
2012-05-22 6:14 ` Artem Bityutskiy [this message]
2012-05-22 7:01 ` Mohammed, Afzal
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=1337667283.2483.83.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@linux.intel.com \
--cc=afzal@ti.com \
--cc=dwmw2@infradead.org \
--cc=ivan.djelic@parrot.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;
as well as URLs for NNTP newsgroup(s).