From: Bjorn Helgaas <helgaas@kernel.org>
To: Bartosz Pawlowski <bartosz.pawlowski@intel.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
sheenamo@google.com, justai@google.com,
andriy.shevchenko@intel.com, joel.a.gibson@intel.com,
emil.s.tantilov@intel.com, gaurav.s.emmanuel@intel.com,
mike.conover@intel.com, shaopeng.he@intel.com,
anthony.l.nguyen@intel.com, pavan.kumar.linga@intel.com
Subject: Re: [PATCH v2 0/2] PCI: Disable ATS for specific Intel IPU E2000 devices
Date: Wed, 18 Oct 2023 16:15:12 -0500 [thread overview]
Message-ID: <20231018211512.GA1378046@bhelgaas> (raw)
In-Reply-To: <20230908143606.685930-1-bartosz.pawlowski@intel.com>
On Fri, Sep 08, 2023 at 02:36:04PM +0000, Bartosz Pawlowski wrote:
> This patch series addresses the problem with A an B steppings of
> Intel IPU E2000 which expects incorrect endianness in data field of ATS
> invalidation request TLP by disabling ATS capability for vulnerable
> devices.
>
> v2:
> - Removed reference to SW workaround in code comment
>
> Bartosz Pawlowski (2):
> PCI: Extract ATS disabling to a helper function
> PCI: Disable ATS for specific Intel IPU E2000 devices
>
> drivers/pci/quirks.c | 35 ++++++++++++++++++++++++++++-------
> 1 file changed, 28 insertions(+), 7 deletions(-)
Applied to pci/ats for v6.7, thanks!
prev parent reply other threads:[~2023-10-18 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:36 [PATCH v2 0/2] PCI: Disable ATS for specific Intel IPU E2000 devices Bartosz Pawlowski
2023-09-08 14:36 ` [PATCH v2 1/2] PCI: Extract ATS disabling to a helper function Bartosz Pawlowski
2023-09-08 14:36 ` [PATCH v2 2/2] PCI: Disable ATS for specific Intel IPU E2000 devices Bartosz Pawlowski
2023-10-18 21:15 ` 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=20231018211512.GA1378046@bhelgaas \
--to=helgaas@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bartosz.pawlowski@intel.com \
--cc=bhelgaas@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=gaurav.s.emmanuel@intel.com \
--cc=joel.a.gibson@intel.com \
--cc=justai@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=mike.conover@intel.com \
--cc=pavan.kumar.linga@intel.com \
--cc=shaopeng.he@intel.com \
--cc=sheenamo@google.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).