From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Mark Brown" <broonie@kernel.org>
Cc: Vijendar.Mukunda@amd.com, venkataprasad.potturu@amd.com,
lgirdwood@gmail.com, perex@perex.cz,
"Takashi Iwai" <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: amd: acp: add Lenovo P16s G5 AMD quirk for legacy SDW machine
Date: Mon, 06 Apr 2026 11:51:20 -0400 [thread overview]
Message-ID: <456cb9ff-e4f2-45cf-b0a0-14c052016c6b@app.fastmail.com> (raw)
In-Reply-To: <177547746630.46304.11552848355240705769.b4-ty@b4>
On Mon, Apr 6, 2026, at 8:11 AM, Mark Brown wrote:
> On Thu, 02 Apr 2026 21:03:25 -0400, Mark Pearson wrote:
>> ASoC: amd: acp: add Lenovo P16s G5 AMD quirk for legacy SDW machine
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.0
>
> Thanks!
>
> [1/1] ASoC: amd: acp: add Lenovo P16s G5 AMD quirk for legacy SDW machine
> https://git.kernel.org/broonie/sound/c/80a7916ca2d9
>
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
Thanks Mark.
Mark
prev parent reply other threads:[~2026-04-06 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 1:03 [PATCH] ASoC: amd: acp: add Lenovo P16s G5 AMD quirk for legacy SDW machine Mark Pearson
2026-04-03 4:20 ` Mukunda,Vijendar
2026-04-06 12:11 ` Mark Brown
2026-04-06 15:51 ` Mark Pearson [this message]
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=456cb9ff-e4f2-45cf-b0a0-14c052016c6b@app.fastmail.com \
--to=mpearson-lenovo@squebb.ca \
--cc=Vijendar.Mukunda@amd.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.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