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/6] ASoC: Intel: machine driver updates for 5.9
Date: Mon, 20 Jul 2020 15:38:44 +0100 [thread overview]
Message-ID: <159525589434.6792.2400800009292925244.b4-ty@kernel.org> (raw)
In-Reply-To: <20200717211337.31956-1-pierre-louis.bossart@linux.intel.com>
On Fri, 17 Jul 2020 16:13:31 -0500, Pierre-Louis Bossart wrote:
> Small patchset to harden the SoundWire machine driver, change bad
> HIDs, update PLL settings and avoid memory leaks. Given that the
> SoundWire core parts are not upstream it's probably not necessary to
> provide the patches to stable branches.
>
> Bard Liao (1):
> ASoC: Intel: sof_sdw_rt711: remove hard-coded codec name
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/6] ASoC: Intel: sof_sdw_rt711: remove hard-coded codec name
(no commit info)
[2/6] ASoC: Intel: sof_sdw_rt711: remove properties in card remove
(no commit info)
[3/6] ASoC: Intel: sof_sdw: add support for systems without i915 audio
(no commit info)
[4/6] ASoC: Intel: sof_sdw: avoid crash if invalid DSP topology loaded
(no commit info)
[5/6] ASoC: intel: board: sof_rt5682: Update rt1015 pll input clk freq
(no commit info)
[6/6] ASoC: Intel: common: change match table ehl-rt5660
commit: 58ef60025a1263e78de01b135d05784996383611
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
next prev parent reply other threads:[~2020-07-20 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 21:13 [PATCH 0/6] ASoC: Intel: machine driver updates for 5.9 Pierre-Louis Bossart
2020-07-17 21:13 ` [PATCH 1/6] ASoC: Intel: sof_sdw_rt711: remove hard-coded codec name Pierre-Louis Bossart
2020-07-17 21:13 ` [PATCH 2/6] ASoC: Intel: sof_sdw_rt711: remove properties in card remove Pierre-Louis Bossart
2020-07-17 21:13 ` [PATCH 3/6] ASoC: Intel: sof_sdw: add support for systems without i915 audio Pierre-Louis Bossart
2020-07-17 21:13 ` [PATCH 4/6] ASoC: Intel: sof_sdw: avoid crash if invalid DSP topology loaded Pierre-Louis Bossart
2020-07-17 21:13 ` [PATCH 5/6] ASoC: intel: board: sof_rt5682: Update rt1015 pll input clk freq Pierre-Louis Bossart
2020-07-17 21:13 ` [PATCH 6/6] ASoC: Intel: common: change match table ehl-rt5660 Pierre-Louis Bossart
2020-07-20 11:51 ` Mark Brown
2020-07-20 14:38 ` Mark Brown [this message]
2020-07-20 15:32 ` [PATCH 0/6] ASoC: Intel: machine driver updates for 5.9 Mark Brown
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=159525589434.6792.2400800009292925244.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.