From: Conor Dooley <conor.dooley@microchip.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Wolfram Sang <wsa@kernel.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: Request for i2c re-inclusion in linux-next
Date: Fri, 26 Jan 2024 08:40:54 +0000 [thread overview]
Message-ID: <20240126-prevail-laboring-3335bb5bfabc@wendy> (raw)
In-Reply-To: <zgjyz7kdovuesyu4s6lfshrsktfozid6hho7xn5ckc4ux54bxj@lkhx4qbdpcki>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
On Fri, Jan 26, 2024 at 07:53:58AM +0100, Andi Shyti wrote:
> Hi Stephen,
>
> > > 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[*].
> > >
> > > Thank you,
> > > Andi
> > >
> > > [*] https://lore.kernel.org/all/20240124225031.3152667-1-andi.shyti@kernel.org/
> >
> > OK, I currently have an i2c tree from Wolfram who is listed as the
> > maintainer, so I need to hear from him (and do you meant to replace his
> > tree, or add another one?).
>
> Yes, I'm going to replace Wolfram's tree. We've been agreeing
> together on this change.
Passing meddler, this tree is just for host controllers and separate
from the i2c subsystem tree, right?
There seems to only be one tree in Next/Trees for the whole subsystem,
rather than one for the subsystem and one for host controllers.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-01-26 8:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 20:28 Request for i2c re-inclusion in linux-next Andi Shyti
2024-01-26 0:50 ` Stephen Rothwell
2024-01-26 6:53 ` Andi Shyti
2024-01-26 8:40 ` Conor Dooley [this message]
2024-01-26 8:59 ` Krzysztof Kozlowski
2024-01-26 13:18 ` Andi Shyti
2024-01-26 13:23 ` Andi Shyti
2024-01-26 13:33 ` Wolfram Sang
2024-01-26 14:12 ` Andi Shyti
2024-01-26 16:22 ` Mark Brown
2024-01-26 8:50 ` Wolfram Sang
2024-01-28 3:28 ` Stephen Rothwell
2024-01-30 12:35 ` Andi Shyti
2024-01-30 23:18 ` Stephen Rothwell
2024-01-31 20:56 ` Stephen Rothwell
2024-01-31 21:49 ` Andi Shyti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240126-prevail-laboring-3335bb5bfabc@wendy \
--to=conor.dooley@microchip.com \
--cc=andi.shyti@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wsa@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox