Message ID | 20120621083650.GA2529@avionic-0098.mockup.avionic-design.de |
---|---|
State | Not Applicable, archived |
Headers | show |
Hi Thierry, On Thu, 21 Jun 2012 10:36:51 +0200 Thierry Reding <thierry.reding@avionic-design.de> wrote: > > The PWM subsystem patches have gone through a number of versions now and > all outstanding issues have been resolved. I believe that the subsystem > is ready for broader testing in linux-next. If all goes well I plan to > submit it to Linus during the 3.6 merge window. > > I am not aware of any dependencies in linux-next. The two patches that > don't touch the PWM subsystem itself are OF related and have been acked > by Rob Herring who prefers that I take them through the PWM tree. > > Please contact me if there are any issues with the tree. > > The following changes since commit cfaf025112d3856637ff34a767ef785ef5cf2ca9: > > Linux 3.5-rc2 (2012-06-08 18:40:09 -0700) > > are available in the git repository at: > > git://gitorious.org/linux-pwm/linux-pwm.git for-next > > for you to fetch changes up to b5156ca503f9471449b941364bb2bc34fa355d5d: > > pwm: Take over maintainership of the PWM subsystem (2012-06-15 12:57:07 +0200) I have added your tree now. 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.