Re: linux-next: New tree -- linux-pstore.git
Hi Anton, On Tue, 21 Aug 2012 19:50:37 -0700 Anton Vorontsov wrote: > > Can you please add linux-pstore.git tree to the linux-next, > the repository address is as follows: > > git://git.infradead.org/users/cbou/linux-pstore.git master > > This tree is dedicated to track pstore infrastructure fixes and > enhancements, currently it holds these commits: > > Anton Vorontsov (3): > pstore/ram: Fix possible NULL dereference > pstore/ram: Mark ramoops_pstore_write_buf() as notrace > MAINTAINERS: Add pstore maintainers > > Jovi Zhang (1): > pstore/ram: Add missing platform_device_unregister > > Randy Dunlap (1): > pstore/ram: Fix printk format warning I have added this tree from today. I note that Linus may require you to GPG sign a tag for him to fetch since your tree is not located on kernel.org (he likes them anyway). I have put just you as the contact in case of problems - if anyone else should also be listed, just let me know. 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 s...@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. pgpZJmD38Yx0w.pgp Description: PGP signature
Re: linux-next: New tree -- linux-pstore.git
Hi Anton, On Tue, 21 Aug 2012 19:50:37 -0700 Anton Vorontsov cbouatmai...@gmail.com wrote: Can you please add linux-pstore.git tree to the linux-next, the repository address is as follows: git://git.infradead.org/users/cbou/linux-pstore.git master This tree is dedicated to track pstore infrastructure fixes and enhancements, currently it holds these commits: Anton Vorontsov (3): pstore/ram: Fix possible NULL dereference pstore/ram: Mark ramoops_pstore_write_buf() as notrace MAINTAINERS: Add pstore maintainers Jovi Zhang (1): pstore/ram: Add missing platform_device_unregister Randy Dunlap (1): pstore/ram: Fix printk format warning I have added this tree from today. I note that Linus may require you to GPG sign a tag for him to fetch since your tree is not located on kernel.org (he likes them anyway). I have put just you as the contact in case of problems - if anyone else should also be listed, just let me know. 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 s...@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. pgpZJmD38Yx0w.pgp Description: PGP signature
Re: linux-next: New tree -- linux-pstore.git
On Tue, Aug 21, 2012 at 7:50 PM, Anton Vorontsov wrote: > Hello Stephen, > > Can you please add linux-pstore.git tree to the linux-next, > the repository address is as follows: > > git://git.infradead.org/users/cbou/linux-pstore.git master > > This tree is dedicated to track pstore infrastructure fixes and > enhancements, currently it holds these commits: > > Anton Vorontsov (3): > pstore/ram: Fix possible NULL dereference > pstore/ram: Mark ramoops_pstore_write_buf() as notrace > MAINTAINERS: Add pstore maintainers > > Jovi Zhang (1): > pstore/ram: Add missing platform_device_unregister > > Randy Dunlap (1): > pstore/ram: Fix printk format warning FWIW, Acked-by: Kees Cook :) -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
linux-next: New tree -- linux-pstore.git
Hello Stephen, Can you please add linux-pstore.git tree to the linux-next, the repository address is as follows: git://git.infradead.org/users/cbou/linux-pstore.git master This tree is dedicated to track pstore infrastructure fixes and enhancements, currently it holds these commits: Anton Vorontsov (3): pstore/ram: Fix possible NULL dereference pstore/ram: Mark ramoops_pstore_write_buf() as notrace MAINTAINERS: Add pstore maintainers Jovi Zhang (1): pstore/ram: Add missing platform_device_unregister Randy Dunlap (1): pstore/ram: Fix printk format warning Thanks! Anton. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
linux-next: New tree -- linux-pstore.git
Hello Stephen, Can you please add linux-pstore.git tree to the linux-next, the repository address is as follows: git://git.infradead.org/users/cbou/linux-pstore.git master This tree is dedicated to track pstore infrastructure fixes and enhancements, currently it holds these commits: Anton Vorontsov (3): pstore/ram: Fix possible NULL dereference pstore/ram: Mark ramoops_pstore_write_buf() as notrace MAINTAINERS: Add pstore maintainers Jovi Zhang (1): pstore/ram: Add missing platform_device_unregister Randy Dunlap (1): pstore/ram: Fix printk format warning Thanks! Anton. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: New tree -- linux-pstore.git
On Tue, Aug 21, 2012 at 7:50 PM, Anton Vorontsov cbouatmai...@gmail.com wrote: Hello Stephen, Can you please add linux-pstore.git tree to the linux-next, the repository address is as follows: git://git.infradead.org/users/cbou/linux-pstore.git master This tree is dedicated to track pstore infrastructure fixes and enhancements, currently it holds these commits: Anton Vorontsov (3): pstore/ram: Fix possible NULL dereference pstore/ram: Mark ramoops_pstore_write_buf() as notrace MAINTAINERS: Add pstore maintainers Jovi Zhang (1): pstore/ram: Add missing platform_device_unregister Randy Dunlap (1): pstore/ram: Fix printk format warning FWIW, Acked-by: Kees Cook keesc...@chromium.org :) -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
