From: "Danilo Krummrich" <dakr@kernel.org>
To: "Johan Hovold" <johan@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] driver core: faux: fix root device registration
Date: Wed, 29 Apr 2026 16:20:18 +0200 [thread overview]
Message-ID: <DI5PDWIV7N7X.16VB7OPUTJ6ZK@kernel.org> (raw)
In-Reply-To: <afHpUxQ5U_4RWjDZ@hovoldconsulting.com>
On Wed Apr 29, 2026 at 1:19 PM CEST, Johan Hovold wrote:
> The stable rules have been relaxed in practice since Autosel. Anything
> that looks like a fix (e.g. has a Fixes tag) gets backported.
>
> And people get tired of asking the stable team to drop patches that were
> not marked for backporting.
There is still a difference between this happening in practice and using that as
a justification to explicitly request a stable backport for something that - by
the official rules - isn't mandated for stable backport.
If the rules changed to the point that they don't apply anymore for deciding
whether to stick Cc: stable on a patch or not, then they should be adjusted
accordingly.
next prev parent reply other threads:[~2026-04-29 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 15:31 [PATCH v2 0/2] driver core: faux: fix root device registration Johan Hovold
2026-04-24 15:31 ` [PATCH v2 1/2] " Johan Hovold
2026-04-28 22:19 ` Danilo Krummrich
2026-04-29 10:17 ` Johan Hovold
2026-04-29 10:47 ` Danilo Krummrich
2026-04-29 11:19 ` Johan Hovold
2026-04-29 14:20 ` Danilo Krummrich [this message]
2026-04-29 15:02 ` Johan Hovold
2026-04-29 20:11 ` Danilo Krummrich
2026-04-30 7:00 ` Greg Kroah-Hartman
2026-04-30 11:29 ` Danilo Krummrich
2026-04-24 15:31 ` [PATCH v2 2/2] driver core: faux: clean up init error handling Johan Hovold
2026-04-29 20:22 ` [PATCH v2 0/2] driver core: faux: fix root device registration Danilo Krummrich
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=DI5PDWIV7N7X.16VB7OPUTJ6ZK@kernel.org \
--to=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--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.