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

You will need to ensure that the patches/commits in your tree/series havebeen: * 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 himto 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 arepublic and will be included in the linux-next trees. You may be sente-mail messages indicating errors or other issues when thepatches/commits from your subsystem tree are merged and tested inlinux-next. These messages may also be cross-posted to the linux-nextmailing list, the linux-kernel mailing list, etc. The linux-next treeproject and IBM (my employer) make no warranties regarding the linux-nextproject, the testing procedures, the results, the e-mails, etc. If youdon't agree to these ground rules, let me know and I'll remove your treefrom participation in linux-next.[unhandled content-type:application/pgp-signature]