Please add battery-fixes tree to linux-next

Please add battery-fixes tree to linux-next

[Sebastian Reichel]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

Hi Stephen,

Could you please add my 'fixes' branch with patches for the current
merge window in addition to the existing 'for-next' branch for the
power-supply subsystem?

battery-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git#fixes

Thanks,

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Please add battery-fixes tree to linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

Hi Sebastian,

On Thu, 9 Jun 2022 21:19:58 +0200 Sebastian Reichel <sre@kernel.org> wrote:
>
> Could you please add my 'fixes' branch with patches for the current
> merge window in addition to the existing 'for-next' branch for the
> power-supply subsystem?
> 
> battery-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git#fixes

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement 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@canb.auug.org.au

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]