From: Takashi Iwai <tiwai@suse.de>
To: Philipp Stanner <phasta@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Clemens Ladisch <clemens@ladisch.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
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>,
linux-parisc@vger.kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] sound: Replace deprecated PCI functions
Date: Fri, 04 Apr 2025 15:47:10 +0200 [thread overview]
Message-ID: <87plhs2g4h.wl-tiwai@suse.de> (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.
>
> So that's being done here. Feel free to squash the patches as you like.
Thanks for the patches. I suppose those are no urgent fixes, and can
be postponed for 6.16? If so, I'll pick them up after 6.15-rc1 merge
window is closed.
Takashi
next prev parent reply other threads:[~2025-04-04 13:47 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 ` Takashi Iwai [this message]
2025-04-04 13:49 ` [PATCH 00/11] sound: " Philipp Stanner
2025-04-07 7:24 ` Takashi Iwai
2025-04-07 23:35 ` (subset) " Mark Brown
2025-04-08 5:22 ` 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=87plhs2g4h.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=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 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.