From: Suman Anna <s-anna@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Jassi Brar <jaswinder.singh@linaro.org>,
Dave Gerlach <d-gerlach@ti.com>,
Markus Mayer <markus.mayer@linaro.org>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv3 0/5] OMAP Mailbox framework adoption & DT support
Date: Tue, 9 Sep 2014 11:15:22 -0500 [thread overview]
Message-ID: <540F279A.1080700@ti.com> (raw)
In-Reply-To: <20140909025225.GI10785@atomide.com>
Hi Tony,
On 09/08/2014 09:52 PM, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [140908 16:21]:
>> * Suman Anna <s-anna@ti.com> [140729 17:37]:
>>> Hi,
>>>
>>> This is an updated version of the OMAP Mailbox framework adoption &
>>> DT support series, refreshed to work with the v9 version of the mailbox
>>> framework [1] from Jassi Brar while also addressing some minor review
>>> comments. Detailed changes are summarized below. Patches are based on
>>> 3.16-rc2.
>>
>> Sorry for the delay, just noticed that I'm supposed to queue
>> these too. I'll queue these into omap-for-v3.18/mailbox against
>> v3.17-rc1 and will probably also merge it into omap-for-v3.18/dt
>> as well.
>
> Actually this is not compiling and seems to probably miss
> the dependencies from Jassi, so dropping the branch.
The last 2 patches which is the framework adoption portion needs the
framework patches from Jassi (as stated in the cover letter). I will
ping on the framework thread to see if it is making it into 3.18. In any
case, we should be able to take the first three patches (2 in drivers
and 1 for DT) - they are independent of the framework and also are
dependencies for the framework adoption patches.
> Anyways, since it seems you need to repost this again, please
> repost the DT changes separately from the driver changes.
Yeah, the other two dependent series are merged for 3.17, so these are
the only patches remaining. I just need to repost them on a 3.17-rc, but
there are no changes required (even with v10 of the framework). So given
above, do you want me to split the first 3 (there is one DT patch) and
post them so that they can be merged for 3.18?
regards
Suman
next prev parent reply other threads:[~2014-09-09 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 0:34 [PATCHv3 0/5] OMAP Mailbox framework adoption & DT support Suman Anna
2014-07-30 0:34 ` [PATCHv3 2/5] mailbox/omap: add support for parsing dt devices Suman Anna
2014-07-30 0:34 ` [PATCHv3 3/5] ARM: dts: OMAP2+: Add sub mailboxes device node information Suman Anna
2014-07-30 0:34 ` [PATCHv3 4/5] mailbox/omap: adapt to the new mailbox framework Suman Anna
2014-07-30 0:34 ` [PATCHv3 5/5] ARM: dts: OMAP2+: Add #mbox-cells property to all mailbox nodes Suman Anna
[not found] ` <1406680479-18446-1-git-send-email-s-anna-l0cyMroinI0@public.gmane.org>
2014-07-30 0:34 ` [PATCHv3 1/5] Documentation: dt: add omap mailbox bindings Suman Anna
2014-09-08 23:20 ` [PATCHv3 0/5] OMAP Mailbox framework adoption & DT support Tony Lindgren
[not found] ` <20140908232053.GS3238-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-09-09 2:52 ` Tony Lindgren
2014-09-09 16:15 ` Suman Anna [this message]
2014-09-11 17:09 ` 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=540F279A.1080700@ti.com \
--to=s-anna@ti.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=markus.mayer@linaro.org \
--cc=pavel@ucw.cz \
--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).