From: Damien Le Moal <dlemoal@kernel.org>
To: Philipp Stanner <pstanner@redhat.com>,
Niklas Cassel <cassel@kernel.org>,
Mikael Pettersson <mikpelinux@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] ATA: Replace deprecated PCI functions
Date: Mon, 9 Dec 2024 10:14:47 +0900 [thread overview]
Message-ID: <973b3b99-77eb-4a27-9a4a-8547d2a2cc76@kernel.org> (raw)
In-Reply-To: <20241204171033.86804-2-pstanner@redhat.com>
On 12/5/24 02:10, Philipp Stanner wrote:
> Hi,
>
> many of you probably know that I'm trying to remove pcim_iomap_regions()
> from the kernel. One of the more difficult users is ATA, because it's
> the only subsystem I've seen so far that accesses that table
> pcim_iomap_table() administrates.
>
> This series only builds as a whole because of patch 1. That's why I
> submit it as an RFC.
>
> I want to know whether you agree with the basic idea, and whether your
> subsystem wants this series to be squashed into a single commit that
> builds.
Overall, looks OK to me. But I think that at least patches 1 and 2 need to be
squashed together. For patch 3, if you can have a minimal "make it compile"
change in patch 2, you can keep the cleanup separate. Otherwise, squashing all
patches together seems fine too.
> Another solution would be to provide a struct ata_host.iomap2 or
> something like that, phase out the pcim_iomap_regions() users, and then
> remove iomap2 again.
That seems unnecessary.
>
> Please tell me your preferred way.
>
> (This is the revived version of an old series from August. In case
> someone is wondering)
>
> Thx,
> P.
>
> Philipp Stanner (3):
> ata: Allocate PCI iomap table statically
> ata: Replace deprecated PCI functions
> libata-sff: Simplify request of PCI resources
>
> drivers/ata/ata_piix.c | 7 +-
> drivers/ata/libata-sff.c | 130 +++++++++++++++++++++++-------------
> drivers/ata/pata_atp867x.c | 13 ++--
> drivers/ata/pata_hpt3x3.c | 10 +--
> drivers/ata/pata_ninja32.c | 11 +--
> drivers/ata/pata_pdc2027x.c | 11 ++-
> drivers/ata/pata_sil680.c | 12 ++--
> drivers/ata/pdc_adma.c | 9 ++-
> drivers/ata/sata_inic162x.c | 10 ++-
> drivers/ata/sata_mv.c | 9 +--
> drivers/ata/sata_nv.c | 8 +--
> drivers/ata/sata_promise.c | 8 ++-
> drivers/ata/sata_qstor.c | 7 +-
> drivers/ata/sata_sil.c | 8 ++-
> drivers/ata/sata_sil24.c | 20 +++---
> drivers/ata/sata_sis.c | 8 +--
> drivers/ata/sata_svw.c | 10 +--
> drivers/ata/sata_sx4.c | 19 +++++-
> drivers/ata/sata_via.c | 31 +++++----
> drivers/ata/sata_vsc.c | 8 ++-
> include/linux/libata.h | 7 +-
> 21 files changed, 216 insertions(+), 140 deletions(-)
>
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2024-12-09 1:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 17:10 [RFC PATCH 0/3] ATA: Replace deprecated PCI functions Philipp Stanner
2024-12-04 17:10 ` [RFC PATCH 1/3] ata: Allocate PCI iomap table statically Philipp Stanner
2024-12-04 17:10 ` [RFC PATCH 2/3] ata: Replace deprecated PCI functions Philipp Stanner
2024-12-12 18:20 ` Sergey Shtylyov
2024-12-04 17:10 ` [RFC PATCH 3/3] libata-sff: Simplify request of PCI resources Philipp Stanner
2024-12-12 19:26 ` Sergey Shtylyov
2024-12-09 1:14 ` Damien Le Moal [this message]
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=973b3b99-77eb-4a27-9a4a-8547d2a2cc76@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpelinux@gmail.com \
--cc=pstanner@redhat.com \
/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