Hi Stephen, On Sun, Jan 28, 2024 at 02:28:04PM +1100, Stephen Rothwell wrote: > On Thu, 25 Jan 2024 21:28:09 +0100 Andi Shyti <andi.shyti@xxxxxxxxxx> 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 Thanks! I have renamed them in my repo as i2c-host and i2c-host-fixes to be aligned with your naming. I'll keep both naming for a while until you decide to update. > both are useful as Mark Brown pointed out. Thanks, Mark! > 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. Thanks, Stephen! Andi
