[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174657893832.4155013.12131767110464880040.b4-ty@kernel.org>
Date: Wed, 07 May 2025 09:48:58 +0900
From: Mark Brown <broonie@...nel.org>
To: Cezary Rojewski <cezary.rojewski@...el.com>,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Daniel Baluta <daniel.baluta@....com>,
Amadeusz Sławiński <amadeuszx.slawinski@...ux.intel.com>,
Damien Le Moal <dlemoal@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Philipp Stanner <phasta@...nel.org>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
sound-open-firmware@...a-project.org
Subject: Re: [PATCH v3 0/4] AsoC: Phase out hybrid PCI devres
On Fri, 25 Apr 2025 10:17:39 +0200, Philipp Stanner wrote:
> Changes in v3:
> - Remove two forgotten calls to pci_release_regions(). (Amadeusz)
> - Adjust commit titles to common format. (Amadeusz, Cezary)
> - Apply RB by Czeray (not everywhere, two patches changed, see point
> 1 above)
>
> Changes in v2:
> - sof: simplify return. (Andy)
> - intel/atom: simplify return. (Andy)
> - Send a separate series for AsoC. (Andy)
> - intel/atom: Add another patch that switches EINVAL to ENOMEM. (Andy)
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: sof: Use pure devres PCI
commit: 45054bb10fd8a545a1feeaab16af1a87ab7fcce3
[2/4] ASoC: intel: avs: Use pure devres PCI
commit: 58fa9c629e29ae921d055c2b7a1e372ae991fb79
[3/4] AsoC: intel: atom: Use pure devres PCI
commit: 938cabc603dc9b040fbfbf7c37b2b48dff8946d4
[4/4] AsoC: intel: atom: Return -ENOMEM if pcim_iomap() fails
commit: 14a3fd030c033453d436233f4c422b4903786ed3
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