* vhost tree for linux-next @ 2011-11-24 20:38 Michael S. Tsirkin 2011-11-24 23:42 ` Stephen Rothwell 2011-11-27 12:48 ` (repost) " Michael S. Tsirkin 0 siblings, 2 replies; 7+ messages in thread From: Michael S. Tsirkin @ 2011-11-24 20:38 UTC (permalink / raw) To: linux-next; +Cc: sfr 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? Thanks! -- MST ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: vhost tree for linux-next 2011-11-24 20:38 vhost tree for linux-next Michael S. Tsirkin @ 2011-11-24 23:42 ` Stephen Rothwell 2011-11-27 12:48 ` (repost) " Michael S. Tsirkin 1 sibling, 0 replies; 7+ messages in thread From: Stephen Rothwell @ 2011-11-24 23:42 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: linux-next [-- Attachment #1: Type: text/plain, Size: 1086 bytes --] Hi Michael, On Thu, 24 Nov 2011 22:38:44 +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? 1) I asked you to cc this request much wider than this (I do not know what is going on in all areas of the kernel, so I rely on feedback from others to determine if stuff should go into linux-next). 2) as fas as I can tell the current contents of that tree was posted for review/feedback for the first time today. Give it a few days for any responses ... -- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ [-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* (repost) vhost tree for linux-next 2011-11-24 20:38 vhost tree for linux-next Michael S. Tsirkin 2011-11-24 23:42 ` Stephen Rothwell @ 2011-11-27 12:48 ` Michael S. Tsirkin 2011-11-27 13:38 ` James Bottomley 2011-11-28 23:36 ` Stephen Rothwell 1 sibling, 2 replies; 7+ messages in thread From: Michael S. Tsirkin @ 2011-11-27 12:48 UTC (permalink / raw) To: linux-next; +Cc: sfr, linux-pci, netdev, linux-scsi 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: (repost) vhost tree for linux-next 2011-11-27 12:48 ` (repost) " Michael S. Tsirkin @ 2011-11-27 13:38 ` James Bottomley 2011-11-27 13:59 ` Michael S. Tsirkin 2011-11-28 23:36 ` Stephen Rothwell 1 sibling, 1 reply; 7+ messages in thread From: James Bottomley @ 2011-11-27 13:38 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: linux-next, sfr, linux-pci, netdev, linux-scsi 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: (repost) vhost tree for linux-next 2011-11-27 13:38 ` James Bottomley @ 2011-11-27 13:59 ` Michael S. Tsirkin 2011-11-27 14:00 ` James Bottomley 0 siblings, 1 reply; 7+ messages in thread From: Michael S. Tsirkin @ 2011-11-27 13:59 UTC (permalink / raw) To: James Bottomley; +Cc: linux-next, sfr, linux-pci, netdev, linux-scsi 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: (repost) vhost tree for linux-next 2011-11-27 13:59 ` Michael S. Tsirkin @ 2011-11-27 14:00 ` James Bottomley 0 siblings, 0 replies; 7+ messages in thread From: James Bottomley @ 2011-11-27 14:00 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: linux-next, sfr, linux-pci, netdev, linux-scsi 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: (repost) vhost tree for linux-next 2011-11-27 12:48 ` (repost) " Michael S. Tsirkin 2011-11-27 13:38 ` James Bottomley @ 2011-11-28 23:36 ` Stephen Rothwell 1 sibling, 0 replies; 7+ messages in thread From: Stephen Rothwell @ 2011-11-28 23:36 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: linux-next, linux-pci, netdev, linux-scsi [-- 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 --] ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-11-28 23:36 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2011-11-24 20:38 vhost tree for linux-next Michael S. Tsirkin 2011-11-24 23:42 ` Stephen Rothwell 2011-11-27 12:48 ` (repost) " Michael S. Tsirkin 2011-11-27 13:38 ` James Bottomley 2011-11-27 13:59 ` Michael S. Tsirkin 2011-11-27 14:00 ` James Bottomley 2011-11-28 23:36 ` Stephen Rothwell
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).