linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Don Dugger <donald.d.dugger@intel.com>
Subject: Re: [PATCH] PCI: Add Patsburg (X79) to Intel PCH root port ACS quirk
Date: Mon, 14 Apr 2014 18:12:07 -0600	[thread overview]
Message-ID: <20140415001207.GE16058@google.com> (raw)
In-Reply-To: <20140331182113.23398.38246.stgit@bling.home>

On Mon, Mar 31, 2014 at 12:21:38PM -0600, Alex Williamson wrote:
> Intel has updated Red Hat bz1037684 to note that X79 PCH root ports
> also provide isolation and the same ACS quirks apply.  Some sources
> indicate additional device IDs for X79, but this patch includes only
> the ones specifically identified by Intel:
> https://bugzilla.redhat.com/show_bug.cgi?id=1037684#c11
> 
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> Cc: Don Dugger <donald.d.dugger@intel.com>

Applied with Don's ack to pci/virtualization for v3.16, thanks!

> ---
>  drivers/pci/quirks.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index e729206..5e4ac63 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -3453,6 +3453,8 @@ static const u16 pci_quirk_intel_pch_acs_ids[] = {
>  	/* Wildcat PCH */
>  	0x9c90, 0x9c91, 0x9c92, 0x9c93, 0x9c94, 0x9c95, 0x9c96, 0x9c97,
>  	0x9c98, 0x9c99, 0x9c9a, 0x9c9b,
> +	/* Patsburg (X79) PCH */
> +	0x1d10, 0x1d12, 0x1d14, 0x1d16, 0x1d18, 0x1d1a, 0x1d1c, 0x1d1e,
>  };
>  
>  static bool pci_quirk_intel_pch_acs_match(struct pci_dev *dev)
> 

      parent reply	other threads:[~2014-04-15  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 18:21 [PATCH] PCI: Add Patsburg (X79) to Intel PCH root port ACS quirk Alex Williamson
2014-04-03 14:45 ` Dugger, Donald D
2014-04-15  0:12 ` 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=20140415001207.GE16058@google.com \
    --to=bhelgaas@google.com \
    --cc=alex.williamson@redhat.com \
    --cc=donald.d.dugger@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).