From: Mark Brown <broonie@kernel.org>
To: Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Yauhen Kharuzhy <jekhor@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Hans de Goede <hansg@kernel.org>
Subject: Re: [PATCH 1/7] ASoC: rt5677: Add 10EC5677 ACPI ID as supported
Date: Wed, 25 Feb 2026 19:06:50 +0000 [thread overview]
Message-ID: <177204641023.168100.17663316355355939070.b4-ty@kernel.org> (raw)
In-Reply-To: <20260211002255.4090440-2-jekhor@gmail.com>
On Wed, 11 Feb 2026 02:18:33 +0200, Yauhen Kharuzhy wrote:
> Add 10EC5677 ACPI ID to the match table. It is used in the Lenovo
> Yoga Book YB1-X91 tablet at least.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: rt5677: Add 10EC5677 ACPI ID as supported
commit: f43aed8dfecb10e95b8235d002990739ebe72c5e
[2/7] ASoC: rt5677: Allow it to be defined as an I2C board
commit: 9f56f0bd2e49876ceeaf9036887fe9b50dfa6b6b
[3/7] ASoC: rt5677: Fix typo in the header file
commit: 687f2679e8bf65bca247ca7f4013130d609e1e56
[4/7] ASoC: rt5677: Report error if the ID register cannot be read
commit: 14848e6a8058916e9b008734aa36da989725b6df
[5/7] ASoC: rt5677: Set up ACPI GPIO pins mapping table
commit: 0cc00de3dd5b66c80e6ec1705ec929f4a45ffa1c
[6/7] ASoC: rt5677: Reset the codec during probing
commit: 904e71d42505ca2af19b0031ffffefc8c1fefb48
[7/7] ASoC: rt5677-spi: Add SPI device ID matching table
commit: bf122191473e26a8f195308b1ba924c98424c8e1
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
next prev parent reply other threads:[~2026-02-25 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 0:18 ASoC rt5677: Prepare to support Lenovo Yoga Book tablets Yauhen Kharuzhy
2026-02-11 0:18 ` [PATCH 1/7] ASoC: rt5677: Add 10EC5677 ACPI ID as supported Yauhen Kharuzhy
2026-02-25 19:06 ` Mark Brown [this message]
2026-02-11 0:18 ` [PATCH 2/7] ASoC: rt5677: Allow it to be defined as an I2C board Yauhen Kharuzhy
2026-02-11 0:18 ` [PATCH 3/7] ASoC: rt5677: Fix typo in the header file Yauhen Kharuzhy
2026-02-11 0:18 ` [PATCH 4/7] ASoC: rt5677: Report error if the ID register cannot be read Yauhen Kharuzhy
2026-02-11 0:18 ` [PATCH 5/7] ASoC: rt5677: Set up ACPI GPIO pins mapping table Yauhen Kharuzhy
2026-02-11 0:18 ` [PATCH 6/7] ASoC: rt5677: Reset the codec during probing Yauhen Kharuzhy
2026-02-11 0:18 ` [PATCH 7/7] ASoC: rt5677-spi: Add SPI device ID matching table Yauhen Kharuzhy
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=177204641023.168100.17663316355355939070.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=hansg@kernel.org \
--cc=jekhor@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--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
all inboxes | Powered by JetHome®