From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/2] iommu: Move Intel and AMD drivers into their own subdirectory
Date: Thu, 4 Jun 2020 08:13:11 +0800 [thread overview]
Message-ID: <148834f4-849e-acf1-c347-e25093aac518@linux.intel.com> (raw)
In-Reply-To: <20200602092616.24638-1-joro@8bytes.org>
Hi Joerg,
On 6/2/20 5:26 PM, Joerg Roedel wrote:
> Hi,
>
> two small patches to move the Intel and AMD IOMMU drivers into their own
> subdirectory under drivers/iommu/ to make the file structure a bit less
> cluttered.
>
Does the MAINTAINERS file need to update?
Best regards,
baolu
> Regards,
>
> Joerg
>
> Joerg Roedel (2):
> iommu/amd: Move AMD IOMMU driver into subdirectory
> iommu/vt-d: Move Intel IOMMU driver into subdirectory
>
> drivers/iommu/Makefile | 18 +++++++++---------
> drivers/iommu/{ => amd}/amd_iommu.h | 0
> drivers/iommu/{ => amd}/amd_iommu_types.h | 0
> .../{amd_iommu_debugfs.c => amd/debugfs.c} | 0
> drivers/iommu/{amd_iommu_init.c => amd/init.c} | 2 +-
> drivers/iommu/{amd_iommu.c => amd/iommu.c} | 2 +-
> .../iommu/{amd_iommu_v2.c => amd/iommu_v2.c} | 0
> .../iommu/{amd_iommu_quirks.c => amd/quirks.c} | 0
> .../{intel-iommu-debugfs.c => intel/debugfs.c} | 0
> drivers/iommu/{ => intel}/dmar.c | 2 +-
> drivers/iommu/{ => intel}/intel-pasid.h | 0
> drivers/iommu/{intel-iommu.c => intel/iommu.c} | 2 +-
> .../irq_remapping.c} | 2 +-
> drivers/iommu/{intel-pasid.c => intel/pasid.c} | 0
> drivers/iommu/{intel-svm.c => intel/svm.c} | 0
> drivers/iommu/{intel-trace.c => intel/trace.c} | 0
> 16 files changed, 14 insertions(+), 14 deletions(-)
> rename drivers/iommu/{ => amd}/amd_iommu.h (100%)
> rename drivers/iommu/{ => amd}/amd_iommu_types.h (100%)
> rename drivers/iommu/{amd_iommu_debugfs.c => amd/debugfs.c} (100%)
> rename drivers/iommu/{amd_iommu_init.c => amd/init.c} (99%)
> rename drivers/iommu/{amd_iommu.c => amd/iommu.c} (99%)
> rename drivers/iommu/{amd_iommu_v2.c => amd/iommu_v2.c} (100%)
> rename drivers/iommu/{amd_iommu_quirks.c => amd/quirks.c} (100%)
> rename drivers/iommu/{intel-iommu-debugfs.c => intel/debugfs.c} (100%)
> rename drivers/iommu/{ => intel}/dmar.c (99%)
> rename drivers/iommu/{ => intel}/intel-pasid.h (100%)
> rename drivers/iommu/{intel-iommu.c => intel/iommu.c} (99%)
> rename drivers/iommu/{intel_irq_remapping.c => intel/irq_remapping.c} (99%)
> rename drivers/iommu/{intel-pasid.c => intel/pasid.c} (100%)
> rename drivers/iommu/{intel-svm.c => intel/svm.c} (100%)
> rename drivers/iommu/{intel-trace.c => intel/trace.c} (100%)
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-06-04 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 9:26 [PATCH 0/2] iommu: Move Intel and AMD drivers into their own subdirectory Joerg Roedel
2020-06-02 9:26 ` [PATCH 1/2] iommu/amd: Move AMD IOMMU driver into subdirectory Joerg Roedel
2020-06-02 9:26 ` [PATCH 2/2] iommu/vt-d: Move Intel " Joerg Roedel
2020-06-03 7:25 ` [PATCH 0/2] iommu: Move Intel and AMD drivers into their own subdirectory Jerry Snitselaar
2020-06-04 0:13 ` Lu Baolu [this message]
2020-06-04 0:33 ` Jerry Snitselaar
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=148834f4-849e-acf1-c347-e25093aac518@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@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).