public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Korotin <igor.korotin@linux.dev>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: Please add rust-i2c-next and rust-i2c-fixes to linux-next
Date: Sat, 4 Apr 2026 16:32:51 +0100	[thread overview]
Message-ID: <01c295bc-4718-49b6-a358-bd7da3e83169@linux.dev> (raw)
In-Reply-To: <adEovA9D9FxlZbbq@sirena.co.uk>



On 4/4/2026 4:05 PM, Mark Brown wrote:
> The fixes branches are generally expected to contain things intended to
> be sent to Linus' tree this cycle rather than material for the next
> merge window, they are merged first and published separately as the
> pending-fixes branch before the rest of the merge proceeds.  People then
> take that branch and do testing on it independently of the rest of -next
> so if it starts acquiring material that's not a bug fix intended to go
> in during the release cycle that might cause confusion.

Ok, I've rebased rust-i2c-fixes to point to 
https://github.com/torvalds/linux.git master.

Thanks
Igor

      reply	other threads:[~2026-04-04 15:32 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
2026-04-04 15:05         ` Mark Brown
2026-04-04 15:32           ` Igor Korotin [this message]

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=01c295bc-4718-49b6-a358-bd7da3e83169@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