(repost) vhost tree for linux-next

(repost) vhost tree for linux-next

[Michael S. Tsirkin]

I normally merge things through Dave, Rusty, Jesse or Jens,
not directly to Linus. However, sometimes there's a large change
(for example, my recent RFC for pci_iomap changes)
where estimating how it interacts with other platforms and planned
changes in the next kernel would be beneficial.

For this purpose, it would be helpful if my tree were added to linux-next.
The tree is:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next

Could you do this please?
(The current contents of that tree was posted for review/feedback
for the first time today.   It might make sense to give it a few days
for any responses ...)

Thanks!

-- 
MST

Re: (repost) vhost tree for linux-next

[James Bottomley]

On Sun, 2011-11-27 at 14:48 +0200, Michael S. Tsirkin wrote:
> I normally merge things through Dave, Rusty, Jesse or Jens,
> not directly to Linus. However, sometimes there's a large change
> (for example, my recent RFC for pci_iomap changes)
> where estimating how it interacts with other platforms and planned
> changes in the next kernel would be beneficial.
> 
> For this purpose, it would be helpful if my tree were added to linux-next.
> The tree is:
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
> 
> Could you do this please?
> (The current contents of that tree was posted for review/feedback
> for the first time today.   It might make sense to give it a few days
> for any responses ...)

I'm a little confused by your to: field.  This is a linux-arch issue,
isn't it, since it's altering architecture implementations of a PCI
function rather than altering anything in SCSI or net?

James

Re: (repost) vhost tree for linux-next

[Michael S. Tsirkin]

On Sun, Nov 27, 2011 at 07:38:59AM -0600, James Bottomley wrote:
> On Sun, 2011-11-27 at 14:48 +0200, Michael S. Tsirkin wrote:
> > I normally merge things through Dave, Rusty, Jesse or Jens,
> > not directly to Linus. However, sometimes there's a large change
> > (for example, my recent RFC for pci_iomap changes)
> > where estimating how it interacts with other platforms and planned
> > changes in the next kernel would be beneficial.
> > 
> > For this purpose, it would be helpful if my tree were added to linux-next.
> > The tree is:
> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
> > 
> > Could you do this please?
> > (The current contents of that tree was posted for review/feedback
> > for the first time today.   It might make sense to give it a few days
> > for any responses ...)
> 
> I'm a little confused by your to: field.  This is a linux-arch issue,
> isn't it, since it's altering architecture implementations of a PCI
> function rather than altering anything in SCSI or net?
> 
> James

Yes. Stephen Rothwell asked me to Cc widely to see if anyone
objects to picking this stuff in linux-next.
Sorry about any confusion.

-- 
MST

Re: (repost) vhost tree for linux-next

[James Bottomley]

On Sun, 2011-11-27 at 15:59 +0200, Michael S. Tsirkin wrote:
> On Sun, Nov 27, 2011 at 07:38:59AM -0600, James Bottomley wrote:
> > On Sun, 2011-11-27 at 14:48 +0200, Michael S. Tsirkin wrote:
> > > I normally merge things through Dave, Rusty, Jesse or Jens,
> > > not directly to Linus. However, sometimes there's a large change
> > > (for example, my recent RFC for pci_iomap changes)
> > > where estimating how it interacts with other platforms and planned
> > > changes in the next kernel would be beneficial.
> > > 
> > > For this purpose, it would be helpful if my tree were added to linux-next.
> > > The tree is:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
> > > 
> > > Could you do this please?
> > > (The current contents of that tree was posted for review/feedback
> > > for the first time today.   It might make sense to give it a few days
> > > for any responses ...)
> > 
> > I'm a little confused by your to: field.  This is a linux-arch issue,
> > isn't it, since it's altering architecture implementations of a PCI
> > function rather than altering anything in SCSI or net?
> > 
> > James
> 
> Yes. Stephen Rothwell asked me to Cc widely to see if anyone
> objects to picking this stuff in linux-next.
> Sorry about any confusion.

I;m fine with that, but the fact that you didn't send it to linux-arch
was more my point ...

James

Re: (repost) vhost tree for linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]

Hi Michael,

On Sun, 27 Nov 2011 14:48:17 +0200 "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> I normally merge things through Dave, Rusty, Jesse or Jens,
> not directly to Linus. However, sometimes there's a large change
> (for example, my recent RFC for pci_iomap changes)
> where estimating how it interacts with other platforms and planned
> changes in the next kernel would be beneficial.
> 
> For this purpose, it would be helpful if my tree were added to linux-next.
> The tree is:
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
> 
> Could you do this please?

I have added this tree from today with just you as the contact.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]