mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
Cc: perex@perex.cz, tiwai@suse.com, srini@kernel.org,
	 alexey.klimov@linaro.org, linux-sound@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: (subset) [PATCH 00/12] ASoC: qcom: q6dsp: few cleanups
Date: Tue, 21 Oct 2025 12:37:17 +0100	[thread overview]
Message-ID: <176104663701.21978.12535064699762499813.b4-ty@kernel.org> (raw)
In-Reply-To: <20251017085307.4325-1-srinivas.kandagatla@oss.qualcomm.com>

On Fri, 17 Oct 2025 09:52:55 +0100, Srinivas Kandagatla wrote:
> This patchset does 3 things.
> - simplify code via __free(kfree) mechanism.
> - use spinlock guards
> - few cleanups discovered during doing above 2.
> 
> No functional changes
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[01/12] ASoC: qdsp6: q6asm: do not sleep while atomic
        commit: fdbb53d318aa94a094434e5f226617f0eb1e8f22

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


      parent reply	other threads:[~2025-10-21 11:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  8:52 Srinivas Kandagatla
2025-10-17  8:52 ` [PATCH 01/12] ASoC: qdsp6: q6asm: do not sleep while atomic Srinivas Kandagatla
2025-10-17  8:52 ` [PATCH 02/12] ASoc: qcom: audioreach: remove unused variables Srinivas Kandagatla
2025-10-17  8:52 ` [PATCH 03/12] ASoc: qcom: audioreach: Use automatic cleanup of kfree() Srinivas Kandagatla
2025-10-17  8:52 ` [PATCH 04/12] ASoc: qcom: q6adm: " Srinivas Kandagatla
2025-10-17  8:53 ` [PATCH 05/12] ASoc: qcom: q6afe: " Srinivas Kandagatla
2025-10-17  8:53 ` [PATCH 06/12] ASoc: qcom: q6apm: " Srinivas Kandagatla
2025-10-17  8:53 ` [PATCH 07/12] ASoc: qcom: q6prm: " Srinivas Kandagatla
2025-10-17  8:53 ` [PATCH 08/12] ASoc: qcom: q6asm: " Srinivas Kandagatla
2025-10-17  8:53 ` [PATCH 09/12] ASoC: qcom: q6afe: Use guard() for spin locks Srinivas Kandagatla
2025-10-17  8:53 ` [PATCH 10/12] ASoC: qcom: q6apm-dai: " Srinivas Kandagatla
2025-10-17  8:53 ` [PATCH 11/12] ASoC: qcom: q6asm-dai: " Srinivas Kandagatla
2025-10-17  8:53 ` [PATCH 12/12] ASoC: qcom: q6asm: " Srinivas Kandagatla
2025-10-19  4:18   ` kernel test robot
2025-10-20 10:29     ` Srinivas Kandagatla
2025-10-21 11:37 ` 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=176104663701.21978.12535064699762499813.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alexey.klimov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=srini@kernel.org \
    --cc=srinivas.kandagatla@oss.qualcomm.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 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®