From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
jbrunet@baylibre.com, broonie@kernel.org
Cc: narmstrong@baylibre.com, linux-amlogic@lists.infradead.org,
khilman@baylibre.com, martin.blumenstingl@googlemail.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v1 0/3] ASoC: meson: Fix mixer-test issues
Date: Thu, 21 Apr 2022 18:24:54 +0100 [thread overview]
Message-ID: <165056189462.376935.4705329277665588764.b4-ty@kernel.org> (raw)
In-Reply-To: <20220421123803.292063-1-broonie@kernel.org>
On Thu, 21 Apr 2022 13:38:00 +0100, Mark Brown wrote:
> These patches fix event generation issues in the custom controls in the
> Meson drivers detected by mixer-test and by inspection once I saw the
> pattern in these drivers. I'm also seeing other failures due to these
> controls having invalid values, eg:
>
> # # AIU ACODEC SRC.0 value 3 more than item count 3
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: meson: Fix event generation for AUI ACODEC mux
commit: 2e3a0d1bfa95b54333f7add3e50e288769373873
[2/3] ASoC: meson: Fix event generation for AUI CODEC mux
commit: fce49921a22262736cdc3cc74fa67915b75e9363
[3/3] ASoC: meson: Fix event generation for G12A tohdmi mux
commit: 12131008fc13ff7f7690d170b7a8f72d24fd7d1e
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
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
jbrunet@baylibre.com, broonie@kernel.org
Cc: martin.blumenstingl@googlemail.com,
linux-amlogic@lists.infradead.org, alsa-devel@alsa-project.org,
khilman@baylibre.com, narmstrong@baylibre.com
Subject: Re: [PATCH v1 0/3] ASoC: meson: Fix mixer-test issues
Date: Thu, 21 Apr 2022 18:24:54 +0100 [thread overview]
Message-ID: <165056189462.376935.4705329277665588764.b4-ty@kernel.org> (raw)
In-Reply-To: <20220421123803.292063-1-broonie@kernel.org>
On Thu, 21 Apr 2022 13:38:00 +0100, Mark Brown wrote:
> These patches fix event generation issues in the custom controls in the
> Meson drivers detected by mixer-test and by inspection once I saw the
> pattern in these drivers. I'm also seeing other failures due to these
> controls having invalid values, eg:
>
> # # AIU ACODEC SRC.0 value 3 more than item count 3
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: meson: Fix event generation for AUI ACODEC mux
commit: 2e3a0d1bfa95b54333f7add3e50e288769373873
[2/3] ASoC: meson: Fix event generation for AUI CODEC mux
commit: fce49921a22262736cdc3cc74fa67915b75e9363
[3/3] ASoC: meson: Fix event generation for G12A tohdmi mux
commit: 12131008fc13ff7f7690d170b7a8f72d24fd7d1e
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:[~2022-04-21 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 12:38 [PATCH v1 0/3] ASoC: meson: Fix mixer-test issues Mark Brown
2022-04-21 12:38 ` Mark Brown
2022-04-21 12:38 ` [PATCH v1 1/3] ASoC: meson: Fix event generation for AUI ACODEC mux Mark Brown
2022-04-21 12:38 ` Mark Brown
2022-04-21 12:38 ` [PATCH v1 2/3] ASoC: meson: Fix event generation for AUI CODEC mux Mark Brown
2022-04-21 12:38 ` Mark Brown
2022-04-21 12:38 ` [PATCH v1 3/3] ASoC: meson: Fix event generation for G12A tohdmi mux Mark Brown
2022-04-21 12:38 ` Mark Brown
2022-04-21 13:02 ` [PATCH v1 0/3] ASoC: meson: Fix mixer-test issues Jerome Brunet
2022-04-21 13:02 ` Jerome Brunet
2022-04-21 13:39 ` Mark Brown
2022-04-21 13:39 ` Mark Brown
2022-04-21 17:24 ` Mark Brown [this message]
2022-04-21 17:24 ` Mark Brown
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=165056189462.376935.4705329277665588764.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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.