From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
stable@vger.kernel.org, linus.walleij@linaro.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH] Revert "gpio: swnode: don't use the swnode's name as the key for GPIO lookup"
Date: Tue, 25 Nov 2025 11:48:02 +0000 [thread overview]
Message-ID: <aSWXcml8rkX99MEy@opensource.cirrus.com> (raw)
In-Reply-To: <2025112531-glance-majorette-40b0@gregkh>
On Tue, Nov 25, 2025 at 12:43:16PM +0100, Greg KH wrote:
> On Tue, Nov 25, 2025 at 11:31:56AM +0100, Bartosz Golaszewski wrote:
> > On Tue, Nov 25, 2025 at 11:29 AM Charles Keepax
> > <ckeepax@opensource.cirrus.com> wrote:
> > >
> > > This reverts commit 25decf0469d4c91d90aa2e28d996aed276bfc622.
> > >
> > > This software node change doesn't actually fix any current issues
> > > with the kernel, it is an improvement to the lookup process rather
> > > than fixing a live bug. It also causes a couple of regressions with
> > > shipping laptops, which relied on the label based lookup.
> > >
> > > There is a fix for the regressions in mainline, the first 5 patches
> > > of [1]. However, those patches are fairly substantial changes and
> > > given the patch causing the regression doesn't actually fix a bug
> > > it seems better to just revert it in stable.
> > >
> > > CC: stable@vger.kernel.org # 6.12, 6.17
> > > Link: https://lore.kernel.org/linux-sound/20251120-reset-gpios-swnodes-v7-0-a100493a0f4b@linaro.org/ [1]
> > > Closes: https://github.com/thesofproject/linux/issues/5599
> > > Closes: https://github.com/thesofproject/linux/issues/5603
> > > Acked-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > > Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> > > ---
> > >
> > > I wasn't exactly sure of the proceedure for reverting a patch that was
> > > cherry-picked to stable, so apologies if I have made any mistakes here
> > > but happy to update if necessary.
> > >
> >
> > Yes, I'd like to stress the fact that this MUST NOT be reverted in
> > mainline, only in v6.12 and v6.17 stable branches.
>
> But why? Why not take the upstream changes instead? We would much
> rather do that as it reduces the divergance. 5 patches is trivial for
> us to take.
My thinking was that they are a bit invasive for backports, as
noted in the commit message. But if that is the preferred option
I can do a series with those instead?
Thanks,
Charles
next prev parent reply other threads:[~2025-11-25 11:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 10:29 [PATCH] Revert "gpio: swnode: don't use the swnode's name as the key for GPIO lookup" Charles Keepax
2025-11-25 10:31 ` Bartosz Golaszewski
2025-11-25 10:49 ` Charles Keepax
2025-11-25 11:43 ` Greg KH
2025-11-25 11:48 ` Charles Keepax [this message]
2025-11-25 11:58 ` Greg KH
2025-11-25 12:49 ` Charles Keepax
2025-11-27 13:51 ` Greg KH
2025-11-27 14:04 ` Charles Keepax
2025-11-27 14:07 ` Greg KH
2025-11-27 14:10 ` Charles Keepax
2025-11-27 14:17 ` Greg KH
2025-11-27 14:45 ` Bartosz Golaszewski
2025-11-27 15:03 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2025-12-16 13:30 Charles Keepax
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=aSWXcml8rkX99MEy@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=patches@opensource.cirrus.com \
--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.