mbox series

[0/4] ASoC: SOF: Kconfig corrections

Message ID 20201111213533.149963-1-pierre-louis.bossart@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: Kconfig corrections | expand

Message

Pierre-Louis Bossart Nov. 11, 2020, 9:35 p.m. UTC
Three cosmetic patches and a fix for a randconfig issue.

Pierre-Louis Bossart (1):
  ASoC: SOF: Intel: fix Kconfig dependency for SND_INTEL_DSP_CONFIG

Randy Dunlap (3):
  ASoC: SOF: imx: fix Kconfig punctuation
  ASoC: SOF: Kconfig: fix Kconfig punctuation and wording
  ASoC: SOF: Intel: fix Kconfig punctuation and wording

 sound/soc/sof/Kconfig       | 42 ++++++++++++------------
 sound/soc/sof/imx/Kconfig   | 10 +++---
 sound/soc/sof/intel/Kconfig | 64 ++++++++++++++++++-------------------
 3 files changed, 58 insertions(+), 58 deletions(-)

Comments

Mark Brown Nov. 12, 2020, 7:39 p.m. UTC | #1
On Wed, 11 Nov 2020 15:35:29 -0600, Pierre-Louis Bossart wrote:
> Three cosmetic patches and a fix for a randconfig issue.
> 
> Pierre-Louis Bossart (1):
>   ASoC: SOF: Intel: fix Kconfig dependency for SND_INTEL_DSP_CONFIG
> 
> Randy Dunlap (3):
>   ASoC: SOF: imx: fix Kconfig punctuation
>   ASoC: SOF: Kconfig: fix Kconfig punctuation and wording
>   ASoC: SOF: Intel: fix Kconfig punctuation and wording
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: SOF: imx: fix Kconfig punctuation
      commit: 724d53f6a0f318390630a50ee713fa19a927fa23
[2/4] ASoC: SOF: Kconfig: fix Kconfig punctuation and wording
      commit: aff581aee84079b89e796d6ab26560c88d1dcd7a
[3/4] ASoC: SOF: Intel: fix Kconfig punctuation and wording
      commit: 66e1b65128c2bf884d39589a8308dd115c5eba67
[4/4] ASoC: SOF: Intel: fix Kconfig dependency for SND_INTEL_DSP_CONFIG
      commit: 358f0ac1f2791c80c19cc26706cf34664c9fd756

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