From: Christoph Hellwig <hch@lst•de>
To: Andreas Larsson <andreas@gaisler•com>
Cc: Christoph Hellwig <hch@lst•de>,
iommu@lists•linux.dev,
Marek Szyprowski <m.szyprowski@samsung•com>,
Robin Murphy <robin.murphy@arm•com>,
Sakari Ailus <sakari.ailus@linux•intel.com>,
Bingbu Cao <bingbu.cao@intel•com>,
"Michael S . Tsirkin" <mst@redhat•com>,
Jason Wang <jasowang@redhat•com>,
linux-kernel@vger•kernel.org, linux-alpha@vger•kernel.org,
linux-arm-kernel@lists•infradead.org, linux-mips@vger•kernel.org,
linux-parisc@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
linux-s390@vger•kernel.org, sparclinux@vger•kernel.org,
linux-media@vger•kernel.org, virtualization@lists•linux.dev,
xen-devel@lists•xenproject.org,
Thomas Gleixner <tglx@linutronix•de>
Subject: Re: [PATCH 2/2] dma-mapping: clearly mark DMA ops as an architecture feature
Date: Thu, 29 Aug 2024 06:30:27 +0200 [thread overview]
Message-ID: <20240829043027.GA4707@lst.de> (raw)
In-Reply-To: <12a0f286-3114-4dac-8b75-3a638d9c8635@gaisler.com>
On Wed, Aug 28, 2024 at 08:21:14AM +0200, Andreas Larsson wrote:
> On 2024-08-28 08:10, Christoph Hellwig wrote:
> > --- a/drivers/xen/Kconfig
> > +++ b/drivers/xen/Kconfig
> > @@ -177,8 +177,8 @@ config XEN_GRANT_DMA_ALLOC
> >
> > config SWIOTLB_XEN
> > def_bool y
> > + depends on ARCH_DMA_OPS
>
> Rename to ARCH_HAS_DMA_OPS in v2 is missing here
Thanks,
I've fixed this up locally now.
next prev parent reply other threads:[~2024-08-29 4:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 6:10 clearly mark DMA_OPS support as an architecture feature v2 Christoph Hellwig
2024-08-28 6:10 ` [PATCH 1/2] vdpa_sim: don't select DMA_OPS Christoph Hellwig
2024-09-03 9:39 ` Michael S. Tsirkin
2024-08-28 6:10 ` [PATCH 2/2] dma-mapping: clearly mark DMA ops as an architecture feature Christoph Hellwig
2024-08-28 6:21 ` Andreas Larsson
2024-08-29 4:30 ` Christoph Hellwig [this message]
2024-09-03 7:27 ` clearly mark DMA_OPS support as an architecture feature v2 Christoph Hellwig
2024-09-03 9:39 ` Michael S. Tsirkin
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=20240829043027.GA4707@lst.de \
--to=hch@lst$(echo .)de \
--cc=andreas@gaisler$(echo .)com \
--cc=bingbu.cao@intel$(echo .)com \
--cc=iommu@lists$(echo .)linux.dev \
--cc=jasowang@redhat$(echo .)com \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-mips@vger$(echo .)kernel.org \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=mst@redhat$(echo .)com \
--cc=robin.murphy@arm$(echo .)com \
--cc=sakari.ailus@linux$(echo .)intel.com \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=tglx@linutronix$(echo .)de \
--cc=virtualization@lists$(echo .)linux.dev \
--cc=xen-devel@lists$(echo .)xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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