[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168487141457.278276.14403684308927400047.b4-ty@kernel.org>
Date: Tue, 23 May 2023 20:50:14 +0100
From: Mark Brown <broonie@...nel.org>
To: perex@...ex.cz, tiwai@...e.com, lgirdwood@...il.com,
oder_chiou@...ltek.com, shengjiu.wang@...il.com,
Xiubo.Lee@...il.com, festevam@...il.com, nicoleotsuka@...il.com,
shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de,
linux-imx@....com, cezary.rojewski@...el.com,
pierre-louis.bossart@...ux.intel.com,
peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
ranjani.sridharan@...ux.intel.com, kai.vehmanen@...ux.intel.com,
matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com,
srinivas.kandagatla@...aro.org, bgoswami@...cinc.com,
vkoul@...nel.org, daniel.baluta@....com, thierry.reding@...il.com,
jonathanh@...dia.com, jarkko.nikula@...mer.com,
Claudiu Beznea <claudiu.beznea@...rochip.com>
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
patches@...nsource.cirrus.com, linuxppc-dev@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
sound-open-firmware@...a-project.org, linux-tegra@...r.kernel.org,
linux-omap@...r.kernel.org
Subject: Re: [PATCH v2 0/2] ASoC: do not include runtime_pm.h if not needed
On Wed, 17 May 2023 12:49:01 +0300, Claudiu Beznea wrote:
> Series removes the pm_runtime.h inclusion in files where
> APIs exported though pm_runtime.h are not used. In case
> of files that make use of pm.h which comes form pm_runtime.h
> added patch 2/2.
>
> Changes were built with allmodconfig on ARM and x86_64 and checked
> all the changed files were built at least once.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: do not include pm_runtime.h if not used
commit: 2f3092e77f98fcfc0d653846591401bfe2a5232e
[2/2] ASoC: use pm.h instead of runtime_pm.h
commit: a9392efae9f5de42673cfc1b81ac6fb88bdb26b2
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
Powered by blists - more mailing lists