From: Igor Korotin <igor.korotin@linux.dev>
To: Mark Brown <broonie@kernel.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: Please add rust-i2c-next and rust-i2c-fixes to linux-next
Date: Sat, 4 Apr 2026 15:50:59 +0100 [thread overview]
Message-ID: <e41bf6d6-810a-455d-81cd-9104d205524e@linux.dev> (raw)
In-Reply-To: <ec1752c1-a170-4473-9ecf-d6d93b31dcd6@sirena.org.uk>
Hello Mark
On 3/30/2026 2:12 PM, Mark Brown wrote:
> On Mon, Mar 30, 2026 at 12:27:55PM +0100, Mark Brown wrote:
>> On Sun, Mar 29, 2026 at 10:59:19AM +1100, Stephen Rothwell wrote:
>>
>>>> Please add the following tree to linux-next:
>>>> Tree: https://github.com/ikrtn/rust-for-linux
>>>> - Branch: rust-i2c-next
>>>> - Branch: rust-i2c-fixes
>>
>>> Mark Brown (cc'd) now maintains the linux-next tree.
>>
>> All being well these should be included from today.
>
> BTW I note that both trees have the same content and that looks like
> -next material, I would expect the -fixes branch to be based on Linus'
> tree and only contain bug fixes.
Both branches currently have identical content because they are newly
created.
If the -fixes branch is expected to be based on Linus’s tree and contain
only bug fixes, I can rebase it accordingly. Please confirm the preferred
base branch.
Thanks
Igor
next prev parent reply other threads:[~2026-04-04 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 21:17 Please add rust-i2c-next and rust-i2c-fixes to linux-next Igor Korotin
2026-03-28 23:59 ` Stephen Rothwell
2026-03-30 11:27 ` Mark Brown
2026-03-30 13:12 ` Mark Brown
2026-04-04 14:50 ` Igor Korotin [this message]
2026-04-04 15:05 ` Mark Brown
2026-04-04 15:32 ` Igor Korotin
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=e41bf6d6-810a-455d-81cd-9104d205524e@linux.dev \
--to=igor.korotin@linux.dev \
--cc=broonie@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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