From: Mark Brown <broonie@kernel.org>
To: Wim Van Boven <wimvanboven@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Mario Limonciello <mario.limonciello@amd.com>,
syed sabakareem <Syed.SabaKareem@amd.com>,
Leohearts <leohearts@leohearts.com>,
Brent Mendelsohn <mendiebm@gmail.com>,
Xiaoyan Li <lxy.lixiaoyan@gmail.com>, linkt <xazrael@hotmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: amd: yc: Add Razer Blade 14 2022 into DMI table
Date: Mon, 26 Dec 2022 23:33:52 +0000 [thread overview]
Message-ID: <167209763231.330820.17564668361422560655.b4-ty@kernel.org> (raw)
In-Reply-To: <20221216081828.12382-1-wimvanboven@gmail.com>
On Fri, 16 Dec 2022 09:18:27 +0100, Wim Van Boven wrote:
> Razer Blade 14 (2022) - RZ09-0427 needs the quirk to enable the built in microphone
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: amd: yc: Add Razer Blade 14 2022 into DMI table
commit: 68506a173dd700c2bd794dcc3489edcdb8ee35c6
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
prev parent reply other threads:[~2022-12-26 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 8:18 Wim Van Boven
2022-12-16 15:09 ` Limonciello, Mario
2022-12-26 23:33 ` Mark Brown [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=167209763231.330820.17564668361422560655.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Syed.SabaKareem@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=leohearts@leohearts.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lxy.lixiaoyan@gmail.com \
--cc=mario.limonciello@amd.com \
--cc=mendiebm@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=wimvanboven@gmail.com \
--cc=xazrael@hotmail.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
all inboxes | Powered by JetHome®