[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231130135133.1031e4b2ca96a288ce2c18d0@linux-foundation.org>
Date: Thu, 30 Nov 2023 13:51:33 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: linux-kernel@...r.kernel.org, Kuan-Ying.Lee@...iatek.com,
Jan Kiszka <jan.kiszka@...mens.com>,
Kieran Bingham <kbingham@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] scripts/gdb: Fix lx-device-list-bus and
lx-device-list-class
On Wed, 29 Nov 2023 20:33:16 -0800 Florian Fainelli <florian.fainelli@...adcom.com> wrote:
> After the conversion to bus_to_subsys() and class_to_subsys(), the gdb
> scripts listing the system buses and classes respectively was broken,
> fix those by returning the subsys_priv pointer and have the various
> caller de-reference either the 'bus' or 'class' structure members
> accordingly.
>
> 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?
My opinion: developers should use Fixes: as a request to -stable
maintainers to target a particular kernel version (and later).
If the developers indeed want to fix both kernel versions then wouldn't
two patches be best?
Powered by blists - more mailing lists