New branches for linux-next
in [Kernel]
|
Prev: Driver core: Fix memory leak on sysdev_class_register error path
Next: USB: gadget: composite: Better string override handling
From: Jeremy Fitzhardinge on 22 Jul 2010 20:00 Hi Stephen, Could you add: git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git upstream/xen This merges cleanly into the current linux-next/master branch. Thanks, J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Stephen Rothwell on 22 Jul 2010 21:20 Hi Jeremy, On Thu, 22 Jul 2010 16:52:40 -0700 Jeremy Fitzhardinge <jeremy(a)goop.org> wrote: > > Could you add: > > git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > upstream/xen Added starting today. I put just you as the contact - I can add more people/lists if you like. 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(a)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.
From: Jeremy Fitzhardinge on 23 Jul 2010 00:20 On 07/22/2010 06:10 PM, Stephen Rothwell wrote: > Added starting today. I put just you as the contact - I can add more > people/lists if you like. > Thanks. Please add "Xen Devel <Xen-devel(a)lists.xensource.com>" to the contact list. J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Stephen Rothwell on 23 Jul 2010 03:10
Hi Jeremy, On Thu, 22 Jul 2010 21:10:19 -0700 Jeremy Fitzhardinge <jeremy(a)goop.org> wrote: > > On 07/22/2010 06:10 PM, Stephen Rothwell wrote: > > Added starting today. I put just you as the contact - I can add more > > people/lists if you like. > > > > Thanks. Please add "Xen Devel <Xen-devel(a)lists.xensource.com>" to the > contact list. Done. -- Cheers, Stephen Rothwell sfr(a)canb.auug.org.au http://www.canb.auug.org.au/~sfr/ |