From: Ohad Ben-Cohen <ohad@wizery.com>
To: Arnd Bergmann <arnd@arndb.de>
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: Fri, 23 Dec 2011 13:45:19 +0200 [thread overview]
Message-ID: <CAK=WgbYanX_q8JDO6MF3zLWMkRiJ6uynmu+s7eBNrX4qL0N8ug@mail.gmail.com> (raw)
In-Reply-To: <201112221522.21146.arnd@arndb.de>
On Thu, Dec 22, 2011 at 5:22 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> 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.
Directly to Linus it is then.
> 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.
Sure, I fully understand.
> 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.
Thanks.
> 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.
I do have explicit Acks on the changes to other sub-systems, though
ideally I'd be happy to have some explicit Acks on the generic code
too.
But I hope this should be fine. Let's try to proceed this way and see
how it goes (maybe I should just tell Linus that despite the lack of
explicit Acks to some of the patches, people do think this is
good-to-go).
Thanks!
Ohad.
next prev parent reply other threads:[~2011-12-23 11:45 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 [this message]
2012-02-01 7:21 ` Ohad Ben-Cohen
2012-02-01 16:57 ` Arnd Bergmann
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='CAK=WgbYanX_q8JDO6MF3zLWMkRiJ6uynmu+s7eBNrX4qL0N8ug@mail.gmail.com' \
--to=ohad@wizery.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--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=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 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).