From: Arnd Bergmann <arnd@arndb.de>
To: "Anna, Suman" <s-anna@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, Olof Johansson <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL 7/7] omap mailbox move to drivers for v3.11 merge window
Date: Fri, 21 Jun 2013 09:39:25 +0200 [thread overview]
Message-ID: <201306210939.26007.arnd@arndb.de> (raw)
In-Reply-To: <37C860A02101E749A747FA2D3C1E3C504CD3DD@DLEE11.ent.ti.com>
On Friday 21 June 2013, Anna, Suman wrote:
> Yes, we still have a plan for a generic subsystem, and these would form the
> the base patches of OMAP adaptation towards that. OMAP mailbox was disabled
> since couple of releases now because of the multi-platform enablement. There were
> couple of different work-items needed on OMAP mailbox like fixing the multi-platform,
> converting to DT and adapting to the new framework. The previous subsystem was
> derived of the OMAP mailbox, so the first and last items were kinda automatic. The
> newest one based on Jassi's work is not gonna reuse any OMAP stuff, so this series
> handles the first one to avoid a huge pending patchset for OMAP on the generic
> framework finalization.
Ok, thanks for the explanation. Please also see the other email thread
about the linux-next conflict.
Arnd
next prev parent reply other threads:[~2013-06-21 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0MFrZm-1V3qHW1bmA-00EJsa@mx.kundenserver.de>
2013-06-20 19:46 ` [GIT PULL 7/7] omap mailbox move to drivers for v3.11 merge window Arnd Bergmann
2013-06-20 22:56 ` Anna, Suman
2013-06-21 7:39 ` Arnd Bergmann [this message]
[not found] <pull-1371578847-800598>
2013-06-18 18:07 ` 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=201306210939.26007.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=s-anna@ti.com \
--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).