From: Mark Brown <broonie@kernel.org>
To: Annaliese McDermond <nh6z@nh6z.net>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"tiwai@suse.com" <tiwai@suse.com>,
"perex@perex.cz" <perex@perex.cz>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: "team@nwdigitalradio.com" <team@nwdigitalradio.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v2 0/2] ASoC: tlv320aic32x4: Bugfixes for tlv320aic32x4 driver
Date: Tue, 6 Apr 2021 18:39:40 +0100 [thread overview]
Message-ID: <161773049107.51713.3511483011411927627.b4-ty@kernel.org> (raw)
In-Reply-To: <010101788984f9d0-64bcaa85-ce13-49dc-bfc6-892a6a4e411e-000000@us-west-2.amazonses.com>
On Wed, 31 Mar 2021 18:21:36 +0000, Annaliese McDermond wrote:
> These are a couple of bugfixes for the tlv320aic32x4 driver
> that we discovered after the Raspberry Pi Foundation's move to
> the 5.10 kernel.
>
> The first increases the maximum value in the regmap configuration
> so that the powerup command actually works.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: tlv320aic32x4: Increase maximum register in regmap
commit: 29654ed8384e9dbaf4cfba689dbcb664a6ab4bb7
[2/2] ASoC: tlv320aic32x4: Register clocks before registering component
commit: 1ca1156cfd69530e6b7cb99943baf90c8bd871a5
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:[~2021-04-06 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210331182125.413693-1-nh6z@nh6z.net>
2021-03-31 18:21 ` [PATCH v2 0/2] ASoC: tlv320aic32x4: Bugfixes for tlv320aic32x4 driver Annaliese McDermond
2021-04-06 17:39 ` Mark Brown [this message]
[not found] ` <20210331182125.413693-3-nh6z@nh6z.net>
2021-03-31 18:21 ` [PATCH v2 2/2] ASoC: tlv320aic32x4: Register clocks before registering component Annaliese McDermond
2021-03-31 18:21 ` Annaliese McDermond
[not found] ` <20210331182125.413693-2-nh6z@nh6z.net>
2021-03-31 18:21 ` [PATCH v2 1/2] ASoC: tlv320aic32x4: Increase maximum register in regmap Annaliese McDermond
2021-03-31 18:21 ` Annaliese McDermond
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=161773049107.51713.3511483011411927627.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=nh6z@nh6z.net \
--cc=perex@perex.cz \
--cc=team@nwdigitalradio.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.