From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de
Subject: Re: [PATCH v2 0/4] ASoC: SOF: Kconfig corrections
Date: Thu, 12 Nov 2020 19:38:57 +0000 [thread overview]
Message-ID: <160520990389.38586.7655538641803522711.b4-ty@kernel.org> (raw)
In-Reply-To: <20201112164425.25603-1-pierre-louis.bossart@linux.intel.com>
On Thu, 12 Nov 2020 10:44:21 -0600, Pierre-Louis Bossart wrote:
> Three cosmetic patches and a fix for a randconfig issue.
>
> v2: rebase to remove git am issue (worked with --3way before)
>
> Pierre-Louis Bossart (1):
> ASoC: SOF: Intel: fix Kconfig dependency for SND_INTEL_DSP_CONFIG
>
> [...]
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
prev parent reply other threads:[~2020-11-12 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 16:44 [PATCH v2 0/4] ASoC: SOF: Kconfig corrections Pierre-Louis Bossart
2020-11-12 16:44 ` [PATCH v2 1/4] ASoC: SOF: imx: fix Kconfig punctuation Pierre-Louis Bossart
2020-11-12 16:44 ` [PATCH v2 2/4] ASoC: SOF: Kconfig: fix Kconfig punctuation and wording Pierre-Louis Bossart
2020-11-12 16:44 ` [PATCH v2 3/4] ASoC: SOF: Intel: " Pierre-Louis Bossart
2020-11-12 16:44 ` [PATCH v2 4/4] ASoC: SOF: Intel: fix Kconfig dependency for SND_INTEL_DSP_CONFIG Pierre-Louis Bossart
2020-11-12 16:46 ` [PATCH v2 0/4] ASoC: SOF: Kconfig corrections Mark Brown
2020-11-12 17:09 ` Pierre-Louis Bossart
2020-11-12 19:38 ` 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=160520990389.38586.7655538641803522711.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.