From: Sasha Levin <sashal@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
peng.fan@nxp.com, Srinivas Kandagatla <srini@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: Patch "ASoC: codec: wcd9335: Convert to GPIO descriptors" has been added to the 6.15-stable tree
Date: Sat, 28 Jun 2025 10:10:49 -0400 [thread overview]
Message-ID: <aF_36YgeZqJW1QLF@lappy> (raw)
In-Reply-To: <CAMRc=McpWPQx2f-7zR9AovKiA1B5BF5QiXHrPXVpT+Xu1uH7cQ@mail.gmail.com>
On Fri, Jun 27, 2025 at 05:34:10PM +0200, Bartosz Golaszewski wrote:
>On Fri, Jun 27, 2025 at 4:04 PM Sasha Levin <sashal@kernel.org> wrote:
>>
>> This is a note to let you know that I've just added the patch titled
>>
>> ASoC: codec: wcd9335: Convert to GPIO descriptors
>>
>> to the 6.15-stable tree which can be found at:
>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>> asoc-codec-wcd9335-convert-to-gpio-descriptors.patch
>> and it can be found in the queue-6.15 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>>
>>
>
>Why is this being backported to stable? It's not a fix, just
>refactoring and updating to a more modern API.
You've cut out the rest of the message, which hase:
> Stable-dep-of: 9079db287fc3 ("ASoC: codecs: wcd9335: Fix missing free of regulator supplies")
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-06-28 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250627140453.808884-1-sashal@kernel.org>
2025-06-27 15:34 ` Patch "ASoC: codec: wcd9335: Convert to GPIO descriptors" has been added to the 6.15-stable tree Bartosz Golaszewski
2025-06-28 14:10 ` Sasha Levin [this message]
2025-06-30 6:48 ` Bartosz Golaszewski
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=aF_36YgeZqJW1QLF@lappy \
--to=sashal@kernel.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=peng.fan@nxp.com \
--cc=perex@perex.cz \
--cc=srini@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
/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