Re: Request for i2c inclusion in linux-next

[Stephen Rothwell <sfr@canb.auug.org.au>]

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

Hi Andi,

On Mon, 31 Jul 2023 00:29:21 +0200 Andi Shyti <andi.shyti@kernel.org> wrote:
>
> could you please include in the linux-next i2c related branches
> from my repository:
> 
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/andi.shyti/linux.git
> 
> the following branches:
> 
> for next:	i2c/andi-for-next
> fixes:		i2c/andi-for-current

Added from tomorrow.  I already have an i2c branch from Wolfram, so I
called your branches i2c-host-fixes and i2c-host.

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

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