From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: <linux-pci@vger.kernel.org>, <bhelgaas@google.com>,
Stefan Assmann <sassmann@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: Add Intel XXV710 to broken INTx masking quirk
Date: Thu, 8 Jun 2017 10:18:33 -0700 [thread overview]
Message-ID: <20170608101833.0000163f@intel.com> (raw)
In-Reply-To: <20170607190027.22611.92564.stgit@gimli.home>
On Wed, 7 Jun 2017 13:00:48 -0600
Alex Williamson <alex.williamson@redhat.com> wrote:
> Just like the other XL710 and X710 variants, the XXV710 device IDs
> appear to have the same hardware bug, the status register doesn't
> report pending interrupts resulting in "irq xx: nobody cared..."
> errors from the spurious interrupt handler when we try to use it
> with device assignment.
Thanks for doing this Alex,
Acked-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
next prev parent reply other threads:[~2017-06-08 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 19:00 [PATCH] PCI: Add Intel XXV710 to broken INTx masking quirk Alex Williamson
2017-06-08 17:18 ` Jesse Brandeburg [this message]
2017-06-12 21:56 ` Bjorn Helgaas
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=20170608101833.0000163f@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sassmann@redhat.com \
/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).