All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Sasha Levin <sashal@kernel.org>,
	Gary Guo <gary@garyguo.net>,
	Chunfeng Song <springbreeze@stu.pku.edu.cn>,
	netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
	fujita.tomonori@gmail.com, kuba@kernel.org, ojeda@kernel.org,
	boqun@kernel.org, hkallweit1@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH net v4] rust: net: phy: fix off-by-one bit positions in device status accessors
Date: Tue, 1 Sep 2026 17:52:24 +0200	[thread overview]
Message-ID: <2026090145-rebuilt-eldercare-9ff3@gregkh> (raw)
In-Reply-To: <CANiq72mXDgdFXy6w1qy=fewJwrjV6ognGrTgNkn_O6zVpzbgYw@mail.gmail.com>

On Tue, Sep 01, 2026 at 02:51:12PM +0200, Miguel Ojeda wrote:
> On Tue, Sep 1, 2026 at 2:48 PM Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > Probably a FAQ, but what is the policy about toolchain versions for
> > stable kernels?
> 
> As far as I understand it, we are supposed to avoid changes unless
> they are truly needed.
> 
> So there can be exceptions, but I doubt we can easily change a minimum
> version without breaking a lot of users (e.g. distributions or users
> using those distributions that have a particular version provided).
> 
> But Cc'ing stable just in case.

Stable kernels should be able to build with newer toolchains, but we
shouldn't break them by forcing a toolchain update unless there is a
very good reason to do so.

thanks,

greg k-h

      reply	other threads:[~2026-09-01 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01  3:18 [PATCH net v4] rust: net: phy: fix off-by-one bit positions in device status accessors Chunfeng Song
2026-09-01 12:03 ` Gary Guo
2026-09-01 12:47   ` Miguel Ojeda
2026-09-01 12:48     ` Miguel Ojeda
2026-09-01 14:44       ` Chunfeng Song
2026-09-01 15:06         ` Miguel Ojeda
2026-09-01 12:48   ` Andrew Lunn
2026-09-01 12:51     ` Miguel Ojeda
2026-09-01 15:52       ` Greg KH [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=2026090145-rebuilt-eldercare-9ff3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew@lunn.ch \
    --cc=boqun@kernel.org \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=springbreeze@stu.pku.edu.cn \
    --cc=stable@vger.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.