From: Mark Brown <broonie@kernel.org>
To: tiwai@suse.de, vkoul@kernel.org,
Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, pierre-louis.bossart@linux.dev,
bard.liao@intel.com, peter.ujfalusi@linux.intel.com
Subject: Re: [PATCH 0/2] ASoC/SoundWire: Simply interrupt enabling for Intel
Date: Sat, 12 Oct 2024 13:50:45 +0100 [thread overview]
Message-ID: <172873744520.3950734.5770397473019892080.b4-ty@kernel.org> (raw)
In-Reply-To: <20241007121241.30914-1-yung-chuan.liao@linux.intel.com>
On Mon, 07 Oct 2024 20:12:39 +0800, Bard Liao wrote:
> It is more logical to couple interrupt enabling/disabling with
> power-up/down sequences.
>
> The change is mainly on ASoC tree. Can we go via ASoC tree with Vinod's
> Acked-by tag?
>
> Pierre-Louis Bossart (2):
> ASoC: SOF: Intel: hda-mlink: expose unlocked interrupt enable routine
> ASoC/SoundWire: Intel: lnl: enable interrupts after first
> power-up/before last power-down
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: SOF: Intel: hda-mlink: expose unlocked interrupt enable routine
commit: eac79786c7397925149a1bfc4bb704777cd42a99
[2/2] ASoC/SoundWire: Intel: lnl: enable interrupts after first power-up/before last power-down
commit: e0941775e6bdcf45e6e20b7ff3bb87dbb7d92fbb
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:[~2024-10-12 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 12:12 [PATCH 0/2] ASoC/SoundWire: Simply interrupt enabling for Intel Bard Liao
2024-10-07 12:12 ` [PATCH 1/2] ASoC: SOF: Intel: hda-mlink: expose unlocked interrupt enable routine Bard Liao
2024-10-07 12:12 ` [PATCH 2/2] ASoC/SoundWire: Intel: lnl: enable interrupts after first power-up/before last power-down Bard Liao
2024-10-11 5:02 ` Vinod Koul
2024-10-12 12:50 ` 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=172873744520.3950734.5770397473019892080.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=bard.liao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=tiwai@suse.de \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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