From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 09:59:02 +0100 [thread overview]
Message-ID: <a4cb4d06-f936-4fbf-92e3-b7465d7ad061@kernel.org> (raw)
In-Reply-To: <zgjyz7kdovuesyu4s6lfshrsktfozid6hho7xn5ckc4ux54bxj@lkhx4qbdpcki>
On 26/01/2024 07:53, 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.
I don't think Wolfram's tree should be dropped. He is your upstream
maintainer:
https://lore.kernel.org/all/ZbNzTKCFxBx9Bz6Y@ninjato/
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-26 8:59 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
2024-01-26 8:59 ` Krzysztof Kozlowski [this message]
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=a4cb4d06-f936-4fbf-92e3-b7465d7ad061@kernel.org \
--to=krzk@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.