From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv3 0/5] OMAP Mailbox framework adoption & DT support
Date: Thu, 11 Sep 2014 10:09:55 -0700 [thread overview]
Message-ID: <20140911170955.GA18849@atomide.com> (raw)
In-Reply-To: <540F279A.1080700@ti.com>
* Suman Anna <s-anna@ti•com> [140909 09:16]:
> 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?
Yes please and looks like you already did thanks :)
Tony
prev parent reply other threads:[~2014-09-11 17:09 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 1/5] Documentation: dt: add omap mailbox bindings 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
2014-09-08 23:20 ` [PATCHv3 0/5] OMAP Mailbox framework adoption & DT support Tony Lindgren
2014-09-09 2:52 ` Tony Lindgren
2014-09-09 16:15 ` Suman Anna
2014-09-11 17:09 ` Tony Lindgren [this message]
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=20140911170955.GA18849@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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