From: Mark Brown <broonie@kernel.org>
To: Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Diogo Ivo <diogo.ivo@bootlin.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH 0/2] ASoC: rt5677: add GPIO get_direction and enable standalone compilation
Date: Mon, 29 Jun 2026 19:41:36 +0100 [thread overview]
Message-ID: <178275849663.47562.8092746831911734388.b4-ty@b4> (raw)
In-Reply-To: <20260620-smaug-audio-v1-0-e318acdf5abd@bootlin.com>
On Sat, 20 Jun 2026 15:50:57 +0200, Diogo Ivo wrote:
> ASoC: rt5677: add GPIO get_direction and enable standalone compilation
>
> This small series fixes two issues in the RT5677 ASoC codec driver:
>
> - Patch 1 adds the missing GPIO .get_direction() callback, allowing
> the direction of GPIO pins to be queried.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.3
Thanks!
[1/2] ASoC: rt5677: Add GPIO .get_direction() callback
https://git.kernel.org/broonie/sound/c/99e361b2a504
[2/2] ASoC: rt5677: Enable standalone compilation for generic card use
https://git.kernel.org/broonie/sound/c/a5edc45d9cf6
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:[~2026-06-30 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 13:50 Diogo Ivo
2026-06-20 13:50 ` [PATCH 1/2] ASoC: rt5677: Add GPIO .get_direction() callback Diogo Ivo
2026-06-22 8:13 ` Bartosz Golaszewski
2026-06-20 13:50 ` [PATCH 2/2] ASoC: rt5677: Enable standalone compilation for generic card use Diogo Ivo
2026-06-29 18:41 ` 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=178275849663.47562.8092746831911734388.b4-ty@b4 \
--to=broonie@kernel.org \
--cc=brgl@kernel.org \
--cc=diogo.ivo@bootlin.com \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--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®