From: Damien Le Moal <dlemoal@kernel.org>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Manivannan Sadhasivami" <manivannan.sadhasivam@linaro.org>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [PATCH v2 1/2] PCI: Rename PCI_IRQ_LEGACY to PCI_IRQ_INTX
Date: Wed, 2 Aug 2023 17:59:57 +0900 [thread overview]
Message-ID: <96150a2a-4036-f443-352f-8a3f15c3c8f1@kernel.org> (raw)
In-Reply-To: <fsfsdc2m6vf4tukmlzgedygowaji2nuntsy2ahnw3sghokydhu@hr3b2s6fnxtm>
On 8/2/23 17:57, Serge Semin wrote:
> On Wed, Aug 02, 2023 at 04:59:43PM +0900, Damien Le Moal wrote:
>> From: Bjorn Helgaas <bhelgaas@google.com>
>>
>> Rename PCI_IRQ_LEGACY to PCI_IRQ_INTX to be more explicit about the type
>> of IRQ being referenced as well as to match the PCI specifications
>> terms. Redefine PCI_IRQ_LEGACY as an alias to PCI_IRQ_INTX to avoid the
>> need for doing the renaming tree-wide. New drivers and new code should
>> now prefer using PCI_IRQ_INTX instead of PCI_IRQ_LEGACY.
>>
>> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
>> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
>> Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
>> ---
>> include/linux/pci.h | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/linux/pci.h b/include/linux/pci.h
>> index 0ff7500772e6..7692d73719e0 100644
>> --- a/include/linux/pci.h
>> +++ b/include/linux/pci.h
>> @@ -1048,11 +1048,13 @@ enum {
>> PCI_SCAN_ALL_PCIE_DEVS = 0x00000040, /* Scan all, not just dev 0 */
>> };
>>
>> -#define PCI_IRQ_LEGACY (1 << 0) /* Allow legacy interrupts */
>> +#define PCI_IRQ_INTX (1 << 0) /* Allow INTx interrupts */
>> #define PCI_IRQ_MSI (1 << 1) /* Allow MSI interrupts */
>> #define PCI_IRQ_MSIX (1 << 2) /* Allow MSI-X interrupts */
>> #define PCI_IRQ_AFFINITY (1 << 3) /* Auto-assign affinity */
>>
>
>> +#define PCI_IRQ_LEGACY PCI_IRQ_INTX /* prefer PCI_IRQ_INTX */
>> +
>
> I would have been more strict about using this macro and explicitly
> stated that the macro is deprecated:
>
> +#define PCI_IRQ_LEGACY PCI_IRQ_INTX /* Deprecated! Use PCI_IRQ_INTX */
> +
Works for me.
Bjorn, Krzysztof,
Do you want me to resend a v3 or can fix that up when applying ?
>
> In anyway:
> Reviewed-by: Serge Semin <fancer.lancer@gmail.com>
>
> -Serge(y)
>
>> /* These external functions are only available when PCI support is enabled */
>> #ifdef CONFIG_PCI
>>
>> --
>> 2.41.0
>>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-08-02 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 7:59 [PATCH v2 0/2] Cleanup IRQ type definitions Damien Le Moal
2023-08-02 7:59 ` [PATCH v2 1/2] PCI: Rename PCI_IRQ_LEGACY to PCI_IRQ_INTX Damien Le Moal
2023-08-02 8:57 ` Serge Semin
2023-08-02 8:59 ` Damien Le Moal [this message]
2023-08-02 7:59 ` [PATCH v2 2/2] PCI: endpoint: Drop PCI_EPC_IRQ_XXX definitions Damien Le Moal
2023-08-02 9:04 ` Serge Semin
2023-08-02 9:08 ` Damien Le Moal
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=96150a2a-4036-f443-352f-8a3f15c3c8f1@kernel.org \
--to=dlemoal@kernel.org \
--cc=bhelgaas@google.com \
--cc=fancer.lancer@gmail.com \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=yoshihiro.shimoda.uh@renesas.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