linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhen Lei <thunder.leizhen@huawei.com>
To: Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	"Joerg Roedel" <joro@8bytes.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	iommu <iommu@lists.linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Yong Wu <yong.wu@mediatek.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	linux-mediatek <linux-mediatek@lists.infradead.org>,
	Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	Jernej Skrabec <jernej.skrabec@siol.net>,
	"David Woodhouse" <dwmw2@infradead.org>,
	Lu Baolu <baolu.lu@linux.intel.com>
Cc: Zhen Lei <thunder.leizhen@huawei.com>
Subject: [PATCH 8/8] iommu/vt-d: fix a couple of spelling mistakes
Date: Fri, 26 Mar 2021 14:24:12 +0800	[thread overview]
Message-ID: <20210326062412.1262-9-thunder.leizhen@huawei.com> (raw)
In-Reply-To: <20210326062412.1262-1-thunder.leizhen@huawei.com>

There are several spelling mistakes, as follows:
guarentees ==> guarantees
resgister ==> register
insufficent ==> insufficient
creats ==> creates
tabke ==> take

Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
---
 drivers/iommu/intel/dmar.c          | 6 +++---
 drivers/iommu/intel/iommu.c         | 2 +-
 drivers/iommu/intel/irq_remapping.c | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/drivers/iommu/intel/dmar.c b/drivers/iommu/intel/dmar.c
index d5c51b5c20aff4b..bb6f0880f6f4db0 100644
--- a/drivers/iommu/intel/dmar.c
+++ b/drivers/iommu/intel/dmar.c
@@ -45,7 +45,7 @@ struct dmar_res_callback {
 
 /*
  * Assumptions:
- * 1) The hotplug framework guarentees that DMAR unit will be hot-added
+ * 1) The hotplug framework guarantees that DMAR unit will be hot-added
  *    before IO devices managed by that unit.
  * 2) The hotplug framework guarantees that DMAR unit will be hot-removed
  *    after IO devices managed by that unit.
@@ -960,10 +960,10 @@ static void unmap_iommu(struct intel_iommu *iommu)
 /**
  * map_iommu: map the iommu's registers
  * @iommu: the iommu to map
- * @phys_addr: the physical address of the base resgister
+ * @phys_addr: the physical address of the base register
  *
  * Memory map the iommu's registers.  Start w/ a single page, and
- * possibly expand if that turns out to be insufficent.
+ * possibly expand if that turns out to be insufficient.
  */
 static int map_iommu(struct intel_iommu *iommu, u64 phys_addr)
 {
diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
index ee0932307d646bb..f9a2277fba99f9f 100644
--- a/drivers/iommu/intel/iommu.c
+++ b/drivers/iommu/intel/iommu.c
@@ -288,7 +288,7 @@ static inline void context_clear_entry(struct context_entry *context)
 
 /*
  * This domain is a statically identity mapping domain.
- *	1. This domain creats a static 1:1 mapping to all usable memory.
+ *	1. This domain creates a static 1:1 mapping to all usable memory.
  * 	2. It maps to each iommu if successful.
  *	3. Each iommu mapps to this domain if successful.
  */
diff --git a/drivers/iommu/intel/irq_remapping.c b/drivers/iommu/intel/irq_remapping.c
index 611ef5243cb63b9..12e9f2cf84e5101 100644
--- a/drivers/iommu/intel/irq_remapping.c
+++ b/drivers/iommu/intel/irq_remapping.c
@@ -74,7 +74,7 @@ struct intel_ir_data {
  *	->iommu->register_lock
  * Note:
  * intel_irq_remap_ops.{supported,prepare,enable,disable,reenable} are called
- * in single-threaded environment with interrupt disabled, so no need to tabke
+ * in single-threaded environment with interrupt disabled, so no need to take
  * the dmar_global_lock.
  */
 DEFINE_RAW_SPINLOCK(irq_2_ir_lock);
-- 
1.8.3



  parent reply	other threads:[~2021-03-26  6:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26  6:24 [PATCH 0/8] iommu: fix a couple of spelling mistakes detected by codespell tool Zhen Lei
2021-03-26  6:24 ` [PATCH 1/8] iommu/pamu: fix a couple of spelling mistakes Zhen Lei
2021-03-26  6:24 ` [PATCH 2/8] iommu/omap: Fix spelling mistake "alignement" -> "alignment" Zhen Lei
2021-03-26  6:24 ` [PATCH 3/8] iommu/mediatek: Fix spelling mistake "phyiscal" -> "physical" Zhen Lei
2021-03-26  6:24 ` [PATCH 4/8] iommu/sun50i: Fix spelling mistake "consits" -> "consists" Zhen Lei
2021-04-17  6:07   ` Jernej Škrabec
2021-03-26  6:24 ` [PATCH 5/8] iommu: fix a couple of spelling mistakes Zhen Lei
2021-04-16 15:55   ` John Garry
2021-04-17  1:10     ` Leizhen (ThunderTown)
2021-03-26  6:24 ` [PATCH 6/8] iommu/amd: " Zhen Lei
2021-03-26  6:24 ` [PATCH 7/8] iommu/arm-smmu: Fix spelling mistake "initally" -> "initially" Zhen Lei
2021-03-26  6:24 ` Zhen Lei [this message]
2021-04-16 15:24 ` [PATCH 0/8] iommu: fix a couple of spelling mistakes detected by codespell tool Joerg Roedel
2021-04-17  1:11   ` Leizhen (ThunderTown)

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=20210326062412.1262-9-thunder.leizhen@huawei.com \
    --to=thunder.leizhen@huawei.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jernej.skrabec@siol.net \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mripard@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=wens@csie.org \
    --cc=will@kernel.org \
    --cc=yong.wu@mediatek.com \
    /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).