linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Grant Likely <grant.likely@secretlab.ca>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Tony Lindgren <tony@atomide.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Brian Swetland <swetland@google.com>
Subject: Re: Linux 3.3-1 out - merge window closed
Date: Tue, 31 Jan 2012 17:56:22 +0100	[thread overview]
Message-ID: <4F281D36.3080604@redhat.com> (raw)
In-Reply-To: <87y5sydjpb.fsf@rustcorp.com.au>

On 01/24/2012 01:32 AM, Rusty Russell wrote:
>> >  >  >
>> >  >  >  * The code is completely self contained, and the only few external
>> >  >  >  places it changes amount to grabbing a new virtio id (which is
>> >  >  >  Acked-by Rusty) and some OMAP init platform code (which is Acked-by
>> >  >  >  Tony). People who aren't explicitly using it won't notice it's there;
>> >  >  >  even its Kconfig entries get selected automatically when relevant
>> >  >  >  (i.e. only on OMAP4 at this point) and would never show up otherwise.
>>  >
>>  >  Hi Linus,
>>  >
>>  >  I'd also like to see this merged.  Rather than going off and inventing
>>  >  something completely new, Ohad has built on the existing virtio
>>  >  infrastructure to implement IPC between CPUs and DSPs running
>>  >  different operating environments.  This is a strong step in the
>>  >  RightDirection(tm) in my opinion and such behaviour should be
>>  >  encouraged.:-)

I didn't see any virtio spec patches for rpmsg, with the result that 
virtio id 7 is being used also by the virtio-scsi patches.  I can 
certainly push virtio-scsi to 8, but perhaps there's something to 
improve on the communication side...

The code for both drivers seems more or less at the same stage ("wait 
for someone to pull", respectively Linus and James Bottomley).

Paolo

  reply	other threads:[~2012-01-31 17:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 23:58 Linux 3.3-1 out - merge window closed Linus Torvalds
2012-01-20  4:14 ` Stephen Rothwell
2012-01-20 17:41   ` Steven Rostedt
2012-01-20 20:15   ` Junio C Hamano
2012-01-22 10:35   ` Geert Uytterhoeven
2012-01-26  9:48   ` Andrew Morton
2012-01-23  9:17 ` Ohad Ben-Cohen
2012-01-23 13:18   ` Grant Likely
2012-01-23 15:18     ` Arnd Bergmann
2012-01-24  0:32       ` Rusty Russell
2012-01-31 16:56         ` Paolo Bonzini [this message]
2012-02-01  2:49           ` Rusty Russell
2012-02-01  6:47             ` Ohad Ben-Cohen
2012-01-23 15:06 ` Carlos Chinea
2012-01-23 19:43   ` Linus Walleij
2012-01-24 18:57     ` Carlos Chinea
2012-01-25 11:35       ` Artem Bityutskiy
2012-01-25 11:47         ` Pekka Enberg
2012-01-25 12:06           ` Artem Bityutskiy

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=4F281D36.3080604@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sboyd@codeaurora.org \
    --cc=swetland@google.com \
    --cc=tony@atomide.com \
    --cc=torvalds@linux-foundation.org \
    /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).