From: Andrew Morton <akpm@linux-foundation.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: linux-kernel@vger.kernel.org, Kuan-Ying.Lee@mediatek.com,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] scripts/gdb: Fix lx-device-list-bus and lx-device-list-class
Date: Thu, 30 Nov 2023 14:30:07 -0800 [thread overview]
Message-ID: <20231130143007.0ca748b966e35426c2cfaa53@linux-foundation.org> (raw)
In-Reply-To: <ae225003-d7a8-41c3-b4f9-a66397512c21@broadcom.com>
On Thu, 30 Nov 2023 14:00:32 -0800 Florian Fainelli <florian.fainelli@broadcom.com> wrote:
> >> Fixes: 83b9148df2c9 ("driver core: bus: bus iterator cleanups")
> >> Fixes: 7b884b7f24b4 ("driver core: class.c: convert to only use class_to_subsys")
> >
> > I don't know how -stable maintainers handle more than one Fixes:. One
> > of the above was released in 6.3, the other in 6.4. What are they to
> > do?
>
> Neither are stable kernels fortunately, so any kernel >= 6.4 where both
> issues are present should be able to cleanly cherry-pick the change.
OK, I'll change it to just 6.4's 7b884b7f24b4 to simplify life.
> I suppose this should have called for me to issue two patches, one
> fixing lx-device-list-bus and the other one fixing lx-device-list-class,
> though it seems like this is such a niche usage that it may not matter
> that much.
It is indeed nichey :)
next prev parent reply other threads:[~2023-11-30 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 4:33 Florian Fainelli
2023-11-30 21:51 ` Andrew Morton
2023-11-30 22:00 ` Florian Fainelli
2023-11-30 22:30 ` Andrew Morton [this message]
2023-12-05 7:00 ` Kuan-Ying Lee (李冠穎)
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=20231130143007.0ca748b966e35426c2cfaa53@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Kuan-Ying.Lee@mediatek.com \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®