Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	 Clemens Ladisch <clemens@ladisch.de>,
	Liam Girdwood <lgirdwood@gmail.com>,
	 Thorsten Blum <thorsten.blum@linux.dev>,
	 Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	 Bard Liao <yung-chuan.liao@linux.intel.com>,
	 Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	 Heiner Kallweit <hkallweit1@gmail.com>,
	 Maxim Mikityanskiy <maxtram95@gmail.com>,
	 Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	 He Lugang <helugang@uniontech.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	 Binbin Zhou <zhoubinbin@loongson.cn>,
	 Tang Bin <tangbin@cmss.chinamobile.com>,
	 Philipp Stanner <phasta@kernel.org>
Cc: linux-parisc@vger.kernel.org, linux-sound@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 00/11] sound: Replace deprecated PCI functions
Date: Tue, 08 Apr 2025 00:35:54 +0100	[thread overview]
Message-ID: <174406895437.1337819.1919250165088744285.b4-ty@kernel.org> (raw)
In-Reply-To: <20250404121911.85277-2-phasta@kernel.org>

On Fri, 04 Apr 2025 14:19:01 +0200, Philipp Stanner wrote:
> pcim_iomap_table() and pcim_iomap_regions() have been deprecated by the
> PCI subsystem. In sound/, they can easily be replaced with
> pcim_iomap_region().
> 
> This series was around some time in late summer last year as a single
> patch. I lost track of it for a while, but Takashi Iwai (AFAIR)
> requested that I split it by component.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[11/11] ASoC: loongson: Replace deprecated PCI functions
        commit: 7288aa73e5cfb3f37ae93b55d7b7d63eca5140a8

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


  parent reply	other threads:[~2025-04-07 23:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 12:19 [PATCH 00/11] sound: Replace deprecated PCI functions Philipp Stanner
2025-04-04 12:19 ` [PATCH 01/11] ALSA: ad1889: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 02/11] ALSA: atiixp: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 03/11] ALSA: au88x0: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 04/11] ALSA: aw2: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 05/11] ALSA: bt87x: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 06/11] ALSA: cs4281: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 07/11] ALSA: hda_intel: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 08/11] ALSA: cs5530: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 09/11] ALSA: lola: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 10/11] ALSA: hdspm: " Philipp Stanner
2025-04-04 12:19 ` [PATCH 11/11] ASoC: loongson: " Philipp Stanner
2025-04-04 13:47 ` [PATCH 00/11] sound: " Takashi Iwai
2025-04-04 13:49   ` Philipp Stanner
2025-04-07  7:24     ` Takashi Iwai
2025-04-07 23:35 ` Mark Brown [this message]
2025-04-08  5:22   ` (subset) " Takashi Iwai
2025-04-08  9:26     ` 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=174406895437.1337819.1919250165088744285.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=clemens@ladisch.de \
    --cc=helugang@uniontech.com \
    --cc=hkallweit1@gmail.com \
    --cc=jbrunet@baylibre.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=maxtram95@gmail.com \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=phasta@kernel.org \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=tangbin@cmss.chinamobile.com \
    --cc=thorsten.blum@linux.dev \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@linux.intel.com \
    --cc=zhoubinbin@loongson.cn \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox