From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, pierre-louis.bossart@linux.intel.com,
daniel.baluta@nxp.com, kai.vehmanen@linux.intel.com,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
ranjani.sridharan@linux.intel.com
Cc: "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.com>,
Jaska Uimonen <jaska.uimonen@linux.intel.com>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:SOUND - SOUND OPEN FIRMWARE SOF DRIVERS"
<sound-open-firmware@alsa-project.org>
Subject: Re: [PATCH] ASoC: SOF: Update correct LED status at the first time usage of update_mute_led()
Date: Fri, 01 May 2020 12:27:23 +0100 [thread overview]
Message-ID: <158833244366.11565.11159142364410757346.b4-ty@kernel.org> (raw)
In-Reply-To: <20200430091139.7003-1-kai.heng.feng@canonical.com>
On Thu, 30 Apr 2020 17:11:39 +0800, Kai-Heng Feng wrote:
> At the first time update_mute_led() gets called, if channels are already
> muted, the temp value equals to led_value as 0, skipping the following
> LED setting.
>
> So set led_value to -1 as an uninitialized state, to update the correct
> LED status at first time usage.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.7
Thanks!
[1/1] ASoC: SOF: Update correct LED status at the first time usage of update_mute_led()
commit: 49c22696348d6e7c8a2ecfd7e60fddfe188ded82
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:[~2020-05-01 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 9:11 Kai-Heng Feng
2020-04-30 17:40 ` Kai Vehmanen
2020-04-30 23:24 ` Ranjani Sridharan
2020-05-01 11:27 ` 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=158833244366.11565.11159142364410757346.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.baluta@nxp.com \
--cc=jaska.uimonen@linux.intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--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®