Hi James,
On Wed, 30 Jul 2014 17:00:29 +0100 James Hogan <james.hogan@xxxxxxxxxx> wrote:
>
> v3.16 is fast approaching and there are quite a few important MIPS
> patches pending. Since Ralf appears to be unavailable at the moment I've
> reviewed and applied some of those patches which are least controversial
> to a fixes branch with the intention of sending a pull request to Ralf &
> Linus so that one of them can hopefully merge it before the release.
>
> Please could the following branch be added to linux-next:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jhogan/mips.git
> branch: mips-fixes
Added from today.
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
sfr@xxxxxxxxxxxxxxxx
Attachment:
signature.asc
Description: PGP signature
