From: Arnd Bergmann <arnd@arndb•de>
To: Ohad Ben-Cohen <ohad@wizery•com>
Cc: linux-arm <linux-arm-kernel@lists•infradead.org>,
linux-kernel@vger•kernel.org, linux-omap@vger•kernel.org,
linux-next@vger•kernel.org,
Grant Likely <grant.likely@secretlab•ca>,
Brian Swetland <swetland@google•com>,
akpm@linux-foundation•org, Greg KH <greg@kroah•com>,
Stephen Boyd <sboyd@codeaurora•org>,
Mark Brown <broonie@opensource•wolfsonmicro.com>,
Rusty Russell <rusty@rustcorp•com.au>,
Russell King <linux@arm•linux.org.uk>,
Tony Lindgren <tony@atomide•com>,
Saravana Kannan <skannan@codeaurora•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Linus Walleij <linus.walleij@linaro•org>
Subject: Re: Adding remoteproc/rpmsg to linux-next
Date: Wed, 1 Feb 2012 16:57:36 +0000 [thread overview]
Message-ID: <201202011657.36998.arnd@arndb.de> (raw)
In-Reply-To: <CAK=WgbZK_fS_rPWZ9pNARia3sp4+jL5GmR0UmyE59WZSObfWEQ@mail.gmail.com>
On Wednesday 01 February 2012, Ohad Ben-Cohen wrote:
> On Thu, Dec 22, 2011 at 5:22 PM, Arnd Bergmann <arnd@arndb•de> wrote:
> > If you think you need more Acks or if there are other
> > reasons to have it go through arm-soc, please tell me and I'll try harder
> > to find the time for a proper review.
>
> Any chance you could carve out some time for reviewing remoteproc and
> rpmsg [1] ?
I will.
> I hope we could either get your Acks on the patches or even have it go
> through arm-soc for 3.4.
Yes, I think it's best to have it merged through arm-soc, in case Linus
is more likely to take it from there than pull from your tree.
Arnd
next prev parent reply other threads:[~2012-02-01 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 14:55 Adding remoteproc/rpmsg to linux-next Ohad Ben-Cohen
2011-12-11 23:33 ` Stephen Rothwell
2011-12-21 17:35 ` Ohad Ben-Cohen
2011-12-22 15:22 ` Arnd Bergmann
2011-12-23 11:45 ` Ohad Ben-Cohen
2012-02-01 7:21 ` Ohad Ben-Cohen
2012-02-01 16:57 ` Arnd Bergmann [this message]
2012-02-01 17:00 ` Ohad Ben-Cohen
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=201202011657.36998.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=akpm@linux-foundation$(echo .)org \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=greg@kroah$(echo .)com \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=linux@arm$(echo .)linux.org.uk \
--cc=ohad@wizery$(echo .)com \
--cc=rusty@rustcorp$(echo .)com.au \
--cc=sboyd@codeaurora$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=skannan@codeaurora$(echo .)org \
--cc=swetland@google$(echo .)com \
--cc=tony@atomide$(echo .)com \
/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