From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH 0/2] Adjust AMD GPU ATS quirks
Date: Wed, 15 Jan 2020 14:17:38 -0600 [thread overview]
Message-ID: <20200115201738.GA190184@google.com> (raw)
In-Reply-To: <CADnq5_Onw1JgtAYiJgkdL55pe5UdVaJ7j-Tmj3THikWEs-nbkQ@mail.gmail.com>
On Wed, Jan 15, 2020 at 12:26:32PM -0500, Alex Deucher wrote:
> On Wed, Jan 15, 2020 at 12:14 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> > On Tue, Jan 14, 2020 at 05:41:44PM -0600, Bjorn Helgaas wrote:
> > > On Tue, Jan 14, 2020 at 03:55:21PM -0500, Alex Deucher wrote:
> > > > We've root caused the issue and clarified the quirk.
> > > > This also adds a new quirk for a new GPU.
> > > >
> > > > Alex Deucher (2):
> > > > pci: Clarify ATS quirk
> > > > pci: add ATS quirk for navi14 board (v2)
> > > >
> > > > drivers/pci/quirks.c | 32 +++++++++++++++++++++++++-------
> > > > 1 file changed, 25 insertions(+), 7 deletions(-)
> > >
> > > I propose the following, which I intend to be functionally identical.
> > > It just doesn't repeat the pci_info() and pdev->ats_cap = 0.
> >
> > Applied to pci/misc for v5.6, thanks!
>
> Can we add this to stable as well?
Done! Do you want it in v5.5? It's pretty localized so looks pretty
low-risk.
next prev parent reply other threads:[~2020-01-15 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 20:55 [PATCH 0/2] Adjust AMD GPU ATS quirks Alex Deucher
2020-01-14 20:55 ` [PATCH 1/2] pci: Clarify ATS quirk Alex Deucher
2020-01-14 20:55 ` [PATCH 2/2] pci: add ATS quirk for navi14 board (v2) Alex Deucher
2020-01-14 23:41 ` [PATCH 0/2] Adjust AMD GPU ATS quirks Bjorn Helgaas
2020-01-15 14:08 ` Deucher, Alexander
2020-01-15 17:14 ` Bjorn Helgaas
2020-01-15 17:26 ` Alex Deucher
2020-01-15 20:17 ` Bjorn Helgaas [this message]
2020-01-15 20:20 ` Alex Deucher
2020-01-15 22:52 ` 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=20200115201738.GA190184@google.com \
--to=helgaas@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.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).