From: Bjorn Helgaas <helgaas@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/ACPI: Update link to PCI firmware specification
Date: Fri, 22 Jul 2022 13:04:29 -0500 [thread overview]
Message-ID: <20220722180429.GA1915025@bhelgaas> (raw)
In-Reply-To: <20220722174754.27921-1-mario.limonciello@amd.com>
On Fri, Jul 22, 2022 at 12:47:54PM -0500, Mario Limonciello wrote:
> The previous link to the PCI firmware specification in the comments
> for drivers/pci/pci-acpi.c no longer works. Update the comment
> to a current link to this specification.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Applied to pci/misc for v5.20, thanks, Mario!
> ---
> drivers/pci/pci-acpi.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/pci-acpi.c b/drivers/pci/pci-acpi.c
> index 3760d85c10d2..a46fec776ad7 100644
> --- a/drivers/pci/pci-acpi.c
> +++ b/drivers/pci/pci-acpi.c
> @@ -21,8 +21,9 @@
> #include "pci.h"
>
> /*
> - * The GUID is defined in the PCI Firmware Specification available here:
> - * https://www.pcisig.com/members/downloads/pcifw_r3_1_13Dec10.pdf
> + * The GUID is defined in the PCI Firmware Specification available
> + * here to PCI-SIG members:
> + * https://members.pcisig.com/wg/PCI-SIG/document/15350
> */
> const guid_t pci_acpi_dsm_guid =
> GUID_INIT(0xe5c937d0, 0x3553, 0x4d7a,
> --
> 2.34.1
>
prev parent reply other threads:[~2022-07-22 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 17:47 [PATCH] PCI/ACPI: Update link to PCI firmware specification Mario Limonciello
2022-07-22 18:04 ` Bjorn Helgaas [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=20220722180429.GA1915025@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).