Hi Stephen,
Might you be willing to include this branch in your linux-next builds?
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git#for-next
It will include OMAP clock, bus architecture, and low-level power
management patches that are planned to be included in pull requests to the
OMAP upstream maintainer, Tony Lindgren. He in turn will submit pull
requests to the arm-soc tree. The objective in including this branch is
to get these patches integration-tested earlier than they would be
otherwise.
regards,
- Paul
* Paul Walmsley <[email protected]> [141219 11:30]:
>
> Hi Stephen,
>
> Might you be willing to include this branch in your linux-next builds?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git#for-next
>
> It will include OMAP clock, bus architecture, and low-level power
> management patches that are planned to be included in pull requests to the
> OMAP upstream maintainer, Tony Lindgren. He in turn will submit pull
> requests to the arm-soc tree. The objective in including this branch is
> to get these patches integration-tested earlier than they would be
> otherwise.
Makes sense to me. The delay in getting omap stuff into Linux next
via arm-soc for-next is just too long because of the large number
of pending pull requests for various ARM SoCs.
While at it, can you please also (re-)add omap for-next too:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git#for-next
Regards,
Tony
Hi Paul,
On Fri, 19 Dec 2014 19:28:08 +0000 (UTC) Paul Walmsley <[email protected]> wrote:
>
> Might you be willing to include this branch in your linux-next builds?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git#for-next
>
> It will include OMAP clock, bus architecture, and low-level power
> management patches that are planned to be included in pull requests to the
> OMAP upstream maintainer, Tony Lindgren. He in turn will submit pull
> requests to the arm-soc tree. The objective in including this branch is
> to get these patches integration-tested earlier than they would be
> otherwise.
Added from today (called "omap" and with you as the contact).
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
[email protected]
Hi Paul,
On Fri, 26 Dec 2014 15:38:22 +1100 Stephen Rothwell <[email protected]> wrote:
>
> On Fri, 19 Dec 2014 19:28:08 +0000 (UTC) Paul Walmsley <[email protected]> wrote:
> >
> > Might you be willing to include this branch in your linux-next builds?
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git#for-next
> >
> > It will include OMAP clock, bus architecture, and low-level power
> > management patches that are planned to be included in pull requests to the
> > OMAP upstream maintainer, Tony Lindgren. He in turn will submit pull
> > requests to the arm-soc tree. The objective in including this branch is
> > to get these patches integration-tested earlier than they would be
> > otherwise.
>
> Added from today (called "omap" and with you as the contact).
Actually called "omap-pending" :-)
--
Cheers,
Stephen Rothwell [email protected]
Hi Tony,
On Fri, 19 Dec 2014 12:02:30 -0800 Tony Lindgren <[email protected]> wrote:
>
> Makes sense to me. The delay in getting omap stuff into Linux next
> via arm-soc for-next is just too long because of the large number
> of pending pull requests for various ARM SoCs.
Maybe that requires a conversation with the arm-soc tree mailtainers ...
> While at it, can you please also (re-)add omap for-next too:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git#for-next
Added from today (called "omap" with you as the contact).
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
[email protected]