mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Saba Kareem Syed <Syed.SabaKareem@amd.com>,
	Sebastian S <iam@decentr.al>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	Xiaoyan Li <lxy.lixiaoyan@gmail.com>,
	Travis Glenn Hansen <travisghansen@yahoo.com>
Subject: Re: [PATCH v2 0/2] Add some models into acp6x quirk list
Date: Wed, 21 Sep 2022 10:25:04 +0100	[thread overview]
Message-ID: <166375230411.526450.3070541932734238859.b4-ty@kernel.org> (raw)
In-Reply-To: <20220920194621.19457-1-mario.limonciello@amd.com>

On Tue, 20 Sep 2022 14:46:19 -0500, Mario Limonciello wrote:
> Another model from ASUS and Lenovo have been identified that
> don't include anything in ACPI tables to indicate they require the
> ACP6x DMIC driver to be loaded.
> 
> This series adds them both to the quirk list.
> 
> changes from v1->v2:
>  * Both models were independently sent in v1 but touch the same code,
>    so v2 collates them together.
> 
> [...]

Applied to

   broonie/sound.git for-next

Thanks!

[1/2] ASoC: amd: yc: Add ASUS UM5302TA into DMI table
      commit: 4df5b13dec9e1b5a12db47ee92eb3f7da5c3deb5
[2/2] ASoC: amd: yc: Add Lenovo Yoga Slim 7 Pro X to quirks table
      commit: 2232b2dd8cd4f1e6d554b2c3f6899ce36f791b67

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

      parent reply	other threads:[~2022-09-21  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 19:46 Mario Limonciello
2022-09-20 19:46 ` [PATCH v2 1/2] ASoC: amd: yc: Add ASUS UM5302TA into DMI table Mario Limonciello
2022-09-20 20:10   ` Mark Brown
2022-09-20 19:46 ` [PATCH v2 2/2] ASoC: amd: yc: Add Lenovo Yoga Slim 7 Pro X to quirks table Mario Limonciello
2022-09-21  9:25 ` 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=166375230411.526450.3070541932734238859.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Syed.SabaKareem@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=iam@decentr.al \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lxy.lixiaoyan@gmail.com \
    --cc=mario.limonciello@amd.com \
    --cc=travisghansen@yahoo.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®