From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>, linux-s390@vger.kernel.org
Cc: Heiko Carstens <hca@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH] s390/pci: Use irq_data_get_msi_desc()
Date: Mon, 14 Nov 2022 09:55:25 +0100 [thread overview]
Message-ID: <b7ec3c33bb8e356fe29f3433002cb31f8013be74.camel@linux.ibm.com> (raw)
In-Reply-To: <8735aoui07.ffs@tglx>
On Sat, 2022-11-12 at 19:47 +0100, Thomas Gleixner wrote:
> No point in doing another lookup of irq_data, it's already provided as
> an argument.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> arch/s390/pci/pci_irq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- a/arch/s390/pci/pci_irq.c
> +++ b/arch/s390/pci/pci_irq.c
> @@ -132,7 +132,7 @@ static int zpci_clear_irq(struct zpci_de
> static int zpci_set_irq_affinity(struct irq_data *data, const struct cpumask *dest,
> bool force)
> {
> - struct msi_desc *entry = irq_get_msi_desc(data->irq);
> + struct msi_desc *entry = irq_data_get_msi_desc(data);
> struct msi_msg msg = entry->msg;
> int cpu_addr = smp_cpu_get_cpu_address(cpumask_first(dest));
>
Thanks for the patch, makes sense to me so have my:
Reviewed-by: Niklas Schnelle <schnelle@linux.ibm.com>
That said it must be noted that this function is only called when using
directed PCI IRQs which is a hardware feature that has not made it to
any released hardware. Nevertheless no point int doing things more
complicated than necessary even for that case.
If there are no objections I'll apply this to our internal tree and it
will then go upstream via the s390 tree.
next prev parent reply other threads:[~2022-11-14 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 18:47 [PATCH] s390/pci: Use irq_data_get_msi_desc() Thomas Gleixner
2022-11-14 8:55 ` Niklas Schnelle [this message]
2022-11-14 9:18 ` Thomas Gleixner
2022-11-14 9:36 ` Alexander Gordeev
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=b7ec3c33bb8e356fe29f3433002cb31f8013be74.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=tglx@linutronix.de \
/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