From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Johan Hovold <johan@kernel.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: Thu, 30 Apr 2026 09:00:06 +0200 [thread overview]
Message-ID: <2026043054-limes-simply-e9ad@gregkh> (raw)
In-Reply-To: <DI5WUT6CUDAN.3SI10HVHF3NWJ@kernel.org>
On Wed, Apr 29, 2026 at 10:11:31PM +0200, Danilo Krummrich wrote:
> On Wed Apr 29, 2026 at 5:02 PM CEST, Johan Hovold wrote:
> > Again, feel free to drop the CC stable tag if you want to.
>
> It's not so much about what I want -- I just try to stay close to what the
> guideline is, and only deviate when there's a good reason.
>
Personally, I think it's good to backport this. I trust Johan here so I
have no objection to taking this for stable trees (nor the other patches
he tagged for stable).
The rules are there for the stable maintainers to say "no" to, not so
much for us to be extremely strict about it at times if it makes sense
to us.
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-30 7:00 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
2026-04-29 15:02 ` Johan Hovold
2026-04-29 20:11 ` Danilo Krummrich
2026-04-30 7:00 ` Greg Kroah-Hartman [this message]
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=2026043054-limes-simply-e9ad@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox