From: Bjorn Helgaas <helgaas@kernel.org>
To: Edward Cree <ecree@solarflare.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
linux-net-drivers@solarflare.com
Subject: Re: [PATCH] pci: quirks: Add ACS quirk to Solarflare SFC9220
Date: Fri, 29 Jul 2016 17:31:27 -0500 [thread overview]
Message-ID: <20160729223127.GA13632@localhost> (raw)
In-Reply-To: <df310014-18d6-0f65-e902-107b04577090@solarflare.com>
On Thu, Jul 28, 2016 at 06:13:56PM +0100, Edward Cree wrote:
> Device does not perform peer-to-peer between functions.
>
> Signed-off-by: Edward Cree <ecree@solarflare.com>
Applied to pci/virtualization. This is tiny, so I think we can squeeze it
in for v4.8.
> ---
> drivers/pci/quirks.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index b69321c..37ff015 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -4095,6 +4095,7 @@ static const struct pci_dev_acs_enabled {
> { PCI_VENDOR_ID_AMD, 0x7809, pci_quirk_amd_sb_acs },
> { PCI_VENDOR_ID_SOLARFLARE, 0x0903, pci_quirk_mf_endpoint_acs },
> { PCI_VENDOR_ID_SOLARFLARE, 0x0923, pci_quirk_mf_endpoint_acs },
> + { PCI_VENDOR_ID_SOLARFLARE, 0x0A03, pci_quirk_mf_endpoint_acs },
> { PCI_VENDOR_ID_INTEL, 0x10C6, pci_quirk_mf_endpoint_acs },
> { PCI_VENDOR_ID_INTEL, 0x10DB, pci_quirk_mf_endpoint_acs },
> { PCI_VENDOR_ID_INTEL, 0x10DD, pci_quirk_mf_endpoint_acs },
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-07-29 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 17:13 [PATCH] pci: quirks: Add ACS quirk to Solarflare SFC9220 Edward Cree
2016-07-29 22:31 ` 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=20160729223127.GA13632@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=ecree@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=linux-pci@vger.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).