From: "Krzysztof Wilczyński" <kw@linux.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: helgaas@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, delineshev@outlook.com
Subject: Re: [PATCH] PCI: Mark Creative Labs EMU20k2 INTx masking as broken
Date: Fri, 13 Sep 2024 21:51:07 +0900 [thread overview]
Message-ID: <20240913125107.GA964006@rocinante> (raw)
In-Reply-To: <20240912215331.839220-1-alex.williamson@redhat.com>
Hello,
> As reported in the link below, a user indicates this device generates
> spurious interrupts when used with vfio-pci unless DisINTx masking
> support is disabled. Quirk the device to mark INTx masking as broken.
Applied to quirks, thank you!
[1/1] PCI: Mark Creative Labs EMU20k2 INTx masking as broken
https://git.kernel.org/pci/pci/c/2910306655a7
Krzysztof
prev parent reply other threads:[~2024-09-13 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 21:53 [PATCH] PCI: Mark Creative Labs EMU20k2 INTx masking as broken Alex Williamson
2024-09-13 12:51 ` Krzysztof Wilczyński [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=20240913125107.GA964006@rocinante \
--to=kw@linux.com \
--cc=alex.williamson@redhat.com \
--cc=delineshev@outlook.com \
--cc=helgaas@kernel.org \
--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