Re: Request for i2c re-inclusion in linux-next

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

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

Hi Andi,

On Thu, 25 Jan 2024 21:28:09 +0100 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/for-next
> fixes:          i2c/for-current
> 
> I have requested this branch to be the main repository for
> collecting i2c host patches[*].

I have added the 2 i2c-host trees using

git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git

i2c/for-current branch is known as i2c-host-fixes
i2c/for-next branch is know as i2c-host

both are useful as Mark Brown pointed out.

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 --]