From: Heiner Kallweit <hkallweit1@gmail.com>
To: Niklas Cassel <cassel@kernel.org>, Philipp Stanner <pstanner@redhat.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
linux-ide@vger.kernel.org,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] ata: ahci: Don't call pci_intx() directly
Date: Mon, 4 Nov 2024 14:23:43 +0100 [thread overview]
Message-ID: <8acdd01c-1744-4545-9cc7-0a60e83a5d4d@gmail.com> (raw)
In-Reply-To: <ZyiGNtLMSY1vTQH7@ryzen>
On 04.11.2024 09:30, Niklas Cassel wrote:
> On Fri, Nov 01, 2024 at 11:38:53PM +0100, Heiner Kallweit wrote:
>> pci_intx() should be called by PCI core and some virtualization code
>> only. In PCI device drivers use the appropriate pci_alloc_irq_vectors()
>> call.
>
> Hello Heiner,
>
> as you might or might not know, this patch conflicts with a Philipp's
> already acked patch:
> https://lore.kernel.org/linux-ide/20241015185124.64726-10-pstanner@redhat.com/
>
I know, therefore he's on cc. Fully migrating PCI device drivers to the
pci_alloc_irq_vectors() should be done anyway and is the cleaner
alternative to changing pci_intx(). However for some drivers this is a rather
complex task, therefore I understand Philipp's approach to adjust pci_intx()
first. He's incorporating other review feedback in his series, so with the
next re-spin he could remove the ahci patch from his series.
>
> Kind regards,
> Niklas
Heiner
next prev parent reply other threads:[~2024-11-04 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 22:38 [PATCH] ata: ahci: Don't call pci_intx() directly Heiner Kallweit
2024-11-04 8:30 ` Niklas Cassel
2024-11-04 13:23 ` Heiner Kallweit [this message]
2024-11-04 18:36 ` Niklas Cassel
2024-11-04 19:40 ` Heiner Kallweit
2024-11-05 15:22 ` Philipp Stanner
2024-11-05 15:51 ` Heiner Kallweit
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=8acdd01c-1744-4545-9cc7-0a60e83a5d4d@gmail.com \
--to=hkallweit1@gmail.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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