mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: shengjiu.wang@gmail.com, Xiubo.Lee@gmail.com, festevam@gmail.com,
	 nicoleotsuka@gmail.com, lgirdwood@gmail.com, perex@perex.cz,
	tiwai@suse.com,  linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org,  linux-sound@vger.kernel.org,
	Chancel Liu <chancel.liu@nxp.com>
Subject: Re: [PATCH v2 0/2] ASoC: fsl_micfil: Set default quality and channel range control
Date: Sat, 29 Nov 2025 01:41:36 +0000	[thread overview]
Message-ID: <176438049657.294473.18267302643868268995.b4-ty@kernel.org> (raw)
In-Reply-To: <20251127022652.674574-1-chancel.liu@nxp.com>

On Thu, 27 Nov 2025 11:26:50 +0900, Chancel Liu wrote:
> Add default quality for different platforms.
> Set channel range control.
> 
> changes in v2
> - use snd_kcontrol_chip() instead of snd_soc_kcontrol_component()
> 
> Chancel Liu (2):
>   ASoC: fsl_micfil: Add default quality for different platforms
>   ASoC: fsl_micfil: Set channel range control
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: fsl_micfil: Add default quality for different platforms
      commit: e04aab96b3776634ab37ddce6d50a431126edec3
[2/2] ASoC: fsl_micfil: Set channel range control
      commit: ef1a7e02fdb7526e8d7c75e744f1f5b2acd7100b

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-11-29  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27  2:26 Chancel Liu
2025-11-27  2:26 ` [PATCH v2 1/2] ASoC: fsl_micfil: Add default quality for different platforms Chancel Liu
2025-11-28  7:42   ` Shengjiu Wang
2025-11-27  2:26 ` [PATCH v2 2/2] ASoC: fsl_micfil: Set channel range control Chancel Liu
2025-11-28  7:44   ` Shengjiu Wang
2025-11-29  1:41 ` 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=176438049657.294473.18267302643868268995.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Xiubo.Lee@gmail.com \
    --cc=chancel.liu@nxp.com \
    --cc=festevam@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nicoleotsuka@gmail.com \
    --cc=perex@perex.cz \
    --cc=shengjiu.wang@gmail.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®