From: Parav Pandit <parav@nvidia.com>
To: <dwmw2@infradead.org>, <baolu.lu@linux.intel.com>,
<iommu@lists.linux-foundation.org>
Cc: will@kernel.org
Subject: [PATCH 0/5] Short cleanups around DMAR
Date: Sun, 30 May 2021 10:50:48 +0300 [thread overview]
Message-ID: <20210530075053.264218-1-parav@nvidia.com> (raw)
Hi David, Lu,
This short series contains small cleanup patches for Intel iommu
in DMAR area.
Patch summary:
Patch-1 uses bitfields for few DMAR capabilities
Patch-2 removes unused iommu_count
Patch-3 removed unnecessary braces
Patch-4 define count data type explicitly as unsigned int
Patch-5 removes unnecessary typecasting
Parav Pandit (5):
iommu/intel: Use bitfields for DMAR capabilities
iommu/intel: Removed unused iommu_count in dmar domain
iommu/intel: Remove unnecessary braces
iommu/intel: Define counter explicitly as unsigned int
iommu/intel: No need to typecast
drivers/iommu/intel/iommu.c | 37 +++++++++++++++----------------------
include/linux/intel-iommu.h | 11 +++++------
2 files changed, 20 insertions(+), 28 deletions(-)
--
2.26.2
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2021-05-30 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 7:50 Parav Pandit [this message]
2021-05-30 7:50 ` [PATCH 1/5] iommu/intel: Use bitfields for DMAR capabilities Parav Pandit
2021-05-30 7:50 ` [PATCH 2/5] iommu/intel: Removed unused iommu_count in dmar domain Parav Pandit
2021-05-30 7:50 ` [PATCH 3/5] iommu/intel: Remove unnecessary braces Parav Pandit
2021-05-30 7:50 ` [PATCH 4/5] iommu/intel: Define counter explicitly as unsigned int Parav Pandit
2021-05-30 7:50 ` [PATCH 5/5] iommu/intel: No need to typecast Parav Pandit
2021-06-09 7:43 ` [PATCH 0/5] Short cleanups around DMAR Lu Baolu
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=20210530075053.264218-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--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 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.