From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Luca Stefani <luca.stefani.ge1@gmail.com>,
Sasha Levin <sashal@kernel.org>, Jiawei Wang <me@jwang.link>,
Mark Brown <broonie@kernel.org>,
linux-sound@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] Revert "ASoC: amd: yc: add new YC platform variant (0x63) support"
Date: Thu, 28 Mar 2024 17:27:58 +0530 [thread overview]
Message-ID: <8e5127ff-0ffa-495a-bd6a-ca452375f5f6@amd.com> (raw)
In-Reply-To: <2024032853-drainage-deflator-5bae@gregkh>
On 28/03/24 17:04, Greg KH wrote:
> On Thu, Mar 28, 2024 at 04:10:38PM +0530, Mukunda,Vijendar wrote:
>> On 27/03/24 23:39, Greg KH wrote:
>>> On Wed, Mar 27, 2024 at 06:56:18PM +0100, Luca Stefani wrote:
>>>> Hello everyone,
>>>>
>>>> Can those changes be pulled in stable? They're currently breaking mic input
>>>> on my 21K9CTO1WW, ThinkPad P16s Gen 2, and probably more devices in the
>>>> wild.
>>> <formletter>
>>>
>>> This is not the correct way to submit patches for inclusion in the
>>> stable kernel tree. Please read:
>>> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>>> for how to do this properly.
>>>
>>> </formletter>
>> These patches already got merged in V6.9-rc1 release.
>> Need to be cherry-picked for stable release.
>>
> What changes exactly? I do not see any git ids here.
>
> confused,
>
> greg k-h
Below are the commits.
37bee1855d0e ASoC: amd: yc: Revert "add new YC platform variant (0x63) support"
861b3415e4de ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo 21J2"
next prev parent reply other threads:[~2024-03-28 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240312023326.224504-1-me@jwang.link>
2024-03-27 17:56 ` [PATCH 0/2] Revert "ASoC: amd: yc: add new YC platform variant (0x63) support" Luca Stefani
2024-03-27 18:09 ` Greg KH
2024-03-28 10:40 ` Mukunda,Vijendar
2024-03-28 11:34 ` Greg KH
2024-03-28 11:57 ` Mukunda,Vijendar [this message]
2024-03-29 9:30 ` Greg KH
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=8e5127ff-0ffa-495a-bd6a-ca452375f5f6@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-sound@vger.kernel.org \
--cc=luca.stefani.ge1@gmail.com \
--cc=me@jwang.link \
--cc=sashal@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