From: Bjorn Helgaas <helgaas@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-pci@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Keith Busch <keith.busch@intel.com>,
Jonathan Derrick <jonathan.derrick@intel.com>
Subject: Re: [PATCH 2/2] x86/pci: Clean up usage of X86_DEV_DMA_OPS
Date: Thu, 11 Apr 2019 08:35:43 -0500 [thread overview]
Message-ID: <20190411133543.GO256045@google.com> (raw)
In-Reply-To: <20190411051849.GA26205@lst.de>
On Thu, Apr 11, 2019 at 07:18:49AM +0200, Christoph Hellwig wrote:
> On Wed, Apr 10, 2019 at 04:45:01PM -0500, Bjorn Helgaas wrote:
> > [+cc Keith, Jonathan (VMD guys)]
> >
> > I'm OK with this from a PCI perspective. It would be nice if
> >
> > dma_domain_list
> > dma_domain_list_lock
> > add_dma_domain()
> > del_dma_domain()
> > set_dma_domain_ops()
> >
> > could all be moved to vmd.c, since they're really only used there.
>
> I have another patch to eventually kill that, but it will need a little
> more prep work and thus be delayed to the next merge window.
Awesome, thanks! I really appreciate all the global cleanup work you do.
Bjorn
next prev parent reply other threads:[~2019-04-11 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 8:02 two small DMA-related Kconfig cleanups for x86 Christoph Hellwig
2019-04-10 8:02 ` [PATCH 1/2] x86: Remove the unused X86_DMA_REMAP kconfig symbol Christoph Hellwig
2019-04-10 8:48 ` [tip:x86/cleanups] x86/Kconfig: Remove the unused X86_DMA_REMAP KConfig symbol tip-bot for Christoph Hellwig
2019-04-10 8:02 ` [PATCH 2/2] x86/pci: Clean up usage of X86_DEV_DMA_OPS Christoph Hellwig
2019-04-10 8:16 ` Ingo Molnar
2019-04-10 21:45 ` Bjorn Helgaas
2019-04-10 22:03 ` Derrick, Jonathan
2019-04-11 5:18 ` Christoph Hellwig
2019-04-11 13:35 ` Bjorn Helgaas [this message]
2019-04-24 5:38 ` Christoph Hellwig
2019-04-24 11:12 ` Ingo Molnar
2019-04-24 12:37 ` [tip:x86/cleanups] " tip-bot for Christoph Hellwig
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=20190411133543.GO256045@google.com \
--to=helgaas@kernel.org \
--cc=hch@lst.de \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.