From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org
Cc: tiwai@suse.de
Subject: Re: [PATCH 0/5] ASoC: SOF: cleanups
Date: Wed, 10 Feb 2021 20:11:36 +0000 [thread overview]
Message-ID: <161298789618.5497.7329014289938073399.b4-ty@kernel.org> (raw)
In-Reply-To: <20210208232149.58899-1-pierre-louis.bossart@linux.intel.com>
On Mon, 8 Feb 2021 17:21:44 -0600, Pierre-Louis Bossart wrote:
> Minor cleanups for error formats, missing cases, useless functions and
> simplifications.
>
> Curtis Malainey (2):
> ASoC: SOF: add missing pm debug
> ASoC: SOF: fix string format for errors
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: SOF: add missing pm debug
commit: a8f50cd9be7cc4c57f29c1390568225ebee90eda
[2/5] ASoC: SOF: fix string format for errors
commit: ce1f55bac5534aa518e26b94728173ee45f91a8c
[3/5] ASoC: SOF: remove unused functions
commit: 3be46fa21088740ae5790d84b882e5a3c98fce41
[4/5] ASoC: SOF: HDA: (cosmetic) simplify hda_dsp_d0i3_work()
commit: f1bb023525fd654121f18f6e2587eeee84c9db04
[5/5] ASoC: SOF: ext_manifest: use explicit number for elem_type
commit: cc11626dd9f894d93ed15d78b04452ca9acbb52b
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:[~2021-02-10 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 23:21 [PATCH 0/5] ASoC: SOF: cleanups Pierre-Louis Bossart
2021-02-08 23:21 ` [PATCH 1/5] ASoC: SOF: add missing pm debug Pierre-Louis Bossart
2021-02-08 23:21 ` [PATCH 2/5] ASoC: SOF: fix string format for errors Pierre-Louis Bossart
2021-02-08 23:21 ` [PATCH 3/5] ASoC: SOF: remove unused functions Pierre-Louis Bossart
2021-02-08 23:21 ` [PATCH 4/5] ASoC: SOF: HDA: (cosmetic) simplify hda_dsp_d0i3_work() Pierre-Louis Bossart
2021-02-08 23:21 ` [PATCH 5/5] ASoC: SOF: ext_manifest: use explicit number for elem_type Pierre-Louis Bossart
2021-02-10 20:11 ` 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=161298789618.5497.7329014289938073399.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.