archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <>
To: "Rafael J . Wysocki" <>,
	Len Brown <>, Bjorn Helgaas <>
Cc: Hans de Goede <>,,
Subject: [PATCH v2] ACPI/PCI: pci_link: use extended_irq union member when setting ext-irq shareable
Date: Mon, 13 Apr 2020 15:09:49 +0200	[thread overview]
Message-ID: <> (raw)

The case ACPI_RESOURCE_TYPE_EXTENDED_IRQ inside acpi_pci_link_set()
is correctly using resource-> for most settings,
but for the shareable setting it so far has accidentally been using
resource-> instead of

Note that the old code happens to also work because the shareable field
offset is the same for both the acpi_resource_irq and
acpi_resource_extended_irq structs.

Acked-by: Bjorn Helgaas <>
Signed-off-by: Hans de Goede <>
Changes in v2:
- Fix some spelling errors in the commit message pointed out by Bjorn
- Add Bjorn's Acked-by
 drivers/acpi/pci_link.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
index 00a6da2121be..ed3d2182cf2c 100644
--- a/drivers/acpi/pci_link.c
+++ b/drivers/acpi/pci_link.c
@@ -322,10 +322,10 @@ static int acpi_pci_link_set(struct acpi_pci_link *link, int irq)
 		resource-> =
 		if (link->irq.triggering == ACPI_EDGE_SENSITIVE)
-			resource-> =
+			resource-> =
-			resource-> = ACPI_SHARED;
+			resource-> = ACPI_SHARED;
 		resource-> = 1;
 		resource->[0] = irq;
 		/* ignore resource_source, it's optional */

             reply	other threads:[~2020-04-13 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 13:09 Hans de Goede [this message]
2020-04-18 19:39 ` [PATCH v2] ACPI/PCI: pci_link: use extended_irq union member when setting ext-irq shareable Rafael J. Wysocki

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).