From: Greg KH <gregkh@linuxfoundation.org>
To: Joshua Peraza <jperaza@google.com>
Cc: rajatja@google.com, baolu.lu@linux.intel.com,
bhelgaas@google.com, dtor@google.com, dwmw2@infradead.org,
helgaas@kernel.org, iommu@lists.linux-foundation.org,
jean-philippe@linaro.org, joro@8bytes.org, jsbarnes@google.com,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
mika.westerberg@linux.intel.com, oohall@gmail.com, pavel@denx.de,
rafael.j.wysocki@intel.com, rafael@kernel.org,
rajatxjain@gmail.com, will@kernel.org
Subject: Re: [PATCH 0/2] PCI/ACPI: Support Microsoft's "DmaProperty"
Date: Thu, 14 Nov 2024 08:27:13 +0100 [thread overview]
Message-ID: <2024111411-mating-granddad-11f6@gregkh> (raw)
In-Reply-To: <20241113202214.1421739-1-jperaza@google.com>
On Wed, Nov 13, 2024 at 08:22:12PM +0000, Joshua Peraza wrote:
> This patchset rebases two previously posted patches supporting
> recognition of Microsoft's DmaProperty.
>
> Rajat Jain (2):
> PCI/ACPI: Support Microsoft's "DmaProperty"
> PCI: Rename pci_dev->untrusted to pci_dev->untrusted_dma
I thought we went through a lot of different choices when picking this
name, and explicitly did NOT use the "_dma" term here for a reason. Can
you go and read those old patch submissions to verify why we did so, and
what has changed since then and then document here what has changed to
allow this name change now?
thanks,
greg k-h
prev parent reply other threads:[~2024-11-14 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 17:21 [PATCH v7 1/2] PCI/ACPI: Support Microsoft's "DmaProperty" Rajat Jain
2022-04-26 17:21 ` [PATCH v7 2/2] PCI: Rename pci_dev->untrusted to pci_dev->untrusted_dma Rajat Jain
2024-11-13 20:22 ` [PATCH 0/2] PCI/ACPI: Support Microsoft's "DmaProperty" Joshua Peraza
2024-11-13 20:22 ` [PATCH 1/2] " Joshua Peraza
2024-11-13 20:22 ` [PATCH 2/2] PCI: Rename pci_dev->untrusted to pci_dev->untrusted_dma Joshua Peraza
2024-11-13 21:38 ` [PATCH 0/2] PCI/ACPI: Support Microsoft's "DmaProperty" Rajat Jain
2024-11-14 7:27 ` Greg KH [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=2024111411-mating-granddad-11f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dtor@google.com \
--cc=dwmw2@infradead.org \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=jperaza@google.com \
--cc=jsbarnes@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=oohall@gmail.com \
--cc=pavel@denx.de \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rajatja@google.com \
--cc=rajatxjain@gmail.com \
--cc=will@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).