Prev: Btrfs: broken file system design (was Unbound(?) internal fragmentation in Btrfs)
Next: rlimits: security, add task_struct to setrlimit
From: Stephen Rothwell on 23 Jun 2010 20:00
On Wed, 23 Jun 2010 09:56:52 +0900 Kukjin Kim <kgene.kim(a)samsung.com> wrote:
> Could you please pull the following into linux-next?
> This tree is for next- Samsung S5P SoCs such as S5P6440, S5P6442, S5PC100,
> and S5PV210/S5PC110.
I have added this from today. I have called the tree s5p. Currently you
alone are the contact for problems to do with this tree - should I add
anyone else (or a mailing list)?
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
* submitted under GPL v2 (or later) and include the Contributor's
* 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.
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.