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: Thu, 22 Dec 2011 15:22:20 +0000 [thread overview]
Message-ID: <201112221522.21146.arnd@arndb.de> (raw)
In-Reply-To: <CAK=WgbZm9txdvZ1VW-iUn5306yMz1Y=DT_Uygwi6zPZNyWx7gA@mail.gmail.com>
On Wednesday 21 December 2011, Ohad Ben-Cohen wrote:
> Hi Arnd,
>
> On Mon, Dec 12, 2011 at 1:33 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > On Fri, 9 Dec 2011 16:55:27 +0200 Ohad Ben-Cohen <ohad@wizery.com> wrote:
> >>
> >> Can you please add the following remoteproc tree to linux-next ?
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git for-next
> >
> > I have added that from today.
>
> Would you like rpmsg/remoteproc to go through arm-soc or do you prefer
> me to send a pull request directly to Linus ?
>
> If you prefer the former (IIRC you told me you might consider it in a
> random ELCE hallway conversation :) then I'll send you a pull request.
>
> I'm happy either way.
Either way works for me, too. Right now, I would tend to let you send it
to Linus directly because I haven't looked at the latest versions of the
code for some time. While I generally trust you to do the right thing
there, I'm not 100% comfortable to vouch for it in the way that an Ack
or pull would imply without doing a more detailed review of the latest
code.
I know that I promised you that review, but haven't gotten to it, sorry.
I've done a 5 minute review now and it absolutely looks good to go in
as far as I can tell, so I certainly don't object to you sending it
to Linus for 3.3. 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.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Adding remoteproc/rpmsg to linux-next
Date: Thu, 22 Dec 2011 15:22:20 +0000 [thread overview]
Message-ID: <201112221522.21146.arnd@arndb.de> (raw)
In-Reply-To: <CAK=WgbZm9txdvZ1VW-iUn5306yMz1Y=DT_Uygwi6zPZNyWx7gA@mail.gmail.com>
On Wednesday 21 December 2011, Ohad Ben-Cohen wrote:
> Hi Arnd,
>
> On Mon, Dec 12, 2011 at 1:33 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > On Fri, 9 Dec 2011 16:55:27 +0200 Ohad Ben-Cohen <ohad@wizery.com> wrote:
> >>
> >> Can you please add the following remoteproc tree to linux-next ?
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git for-next
> >
> > I have added that from today.
>
> Would you like rpmsg/remoteproc to go through arm-soc or do you prefer
> me to send a pull request directly to Linus ?
>
> If you prefer the former (IIRC you told me you might consider it in a
> random ELCE hallway conversation :) then I'll send you a pull request.
>
> I'm happy either way.
Either way works for me, too. Right now, I would tend to let you send it
to Linus directly because I haven't looked at the latest versions of the
code for some time. While I generally trust you to do the right thing
there, I'm not 100% comfortable to vouch for it in the way that an Ack
or pull would imply without doing a more detailed review of the latest
code.
I know that I promised you that review, but haven't gotten to it, sorry.
I've done a 5 minute review now and it absolutely looks good to go in
as far as I can tell, so I certainly don't object to you sending it
to Linus for 3.3. 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.
Arnd
next prev parent reply other threads:[~2011-12-22 15:22 UTC|newest]
Thread overview: 16+ 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-09 14:55 ` Ohad Ben-Cohen
2011-12-11 23:33 ` Stephen Rothwell
2011-12-11 23:33 ` Stephen Rothwell
2011-12-21 17:35 ` Ohad Ben-Cohen
2011-12-21 17:35 ` Ohad Ben-Cohen
2011-12-22 15:22 ` Arnd Bergmann [this message]
2011-12-22 15:22 ` Arnd Bergmann
2011-12-23 11:45 ` Ohad Ben-Cohen
2011-12-23 11:45 ` Ohad Ben-Cohen
2012-02-01 7:21 ` Ohad Ben-Cohen
2012-02-01 7:21 ` Ohad Ben-Cohen
2012-02-01 16:57 ` Arnd Bergmann
2012-02-01 16:57 ` Arnd Bergmann
2012-02-01 17:00 ` Ohad Ben-Cohen
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=201112221522.21146.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ohad@wizery.com \
--cc=rusty@rustcorp.com.au \
--cc=sboyd@codeaurora.org \
--cc=sfr@canb.auug.org.au \
--cc=skannan@codeaurora.org \
--cc=swetland@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.