From: Joerg Roedel <jroedel@suse.de>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-pci@vger.kernel.org, Lu Baolu <baolu.lu@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Kevin Tian <kevin.tian@intel.com>,
kernel test robot <lkp@intel.com>,
patches@lists.linux.dev
Subject: Re: [PATCH] PCI/ATS: Add missing pci_prepare_ats() stub
Date: Fri, 30 Aug 2024 14:30:13 +0200 [thread overview]
Message-ID: <ZtG7VXSsmDbt4a3I@suse.de> (raw)
In-Reply-To: <0-v1-3ff295fa1528+d7-pci_prepare_ats_proto_jgg@nvidia.com>
On Wed, Aug 14, 2024 at 07:20:52PM -0300, Jason Gunthorpe wrote:
> Surprised 0-day didn't catch this before it made it to linux-next, but here it
> is..
>
> Joerg if you can squash it that would be great.
Done, thanks.
--
Jörg Rödel
jroedel@suse.de
SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany
https://www.suse.com/
Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich
(HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2024-08-30 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 22:20 [PATCH] PCI/ATS: Add missing pci_prepare_ats() stub Jason Gunthorpe
2024-08-30 12:30 ` Joerg Roedel [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=ZtG7VXSsmDbt4a3I@suse.de \
--to=jroedel@suse.de \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=patches@lists.linux.dev \
/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