From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
"David Woodhouse" <dwmw2@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Yong Wu <yong.wu@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
"Maxime Ripard" <mripard@kernel.org>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
iommu <iommu@lists.linux-foundation.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-mediatek <linux-mediatek@lists.infradead.org>,
linux-sunxi <linux-sunxi@lists.linux.dev>
Subject: Re: [PATCH v2 1/1] iommu: Clear a lot of spelling mistakes
Date: Wed, 9 Jun 2021 09:41:07 +0800 [thread overview]
Message-ID: <6c5d2840-c329-1e23-00ac-b063dd0d2b74@huawei.com> (raw)
In-Reply-To: <20210608093845.GC8935@willie-the-truck>
On 2021/6/8 17:38, Will Deacon wrote:
> On Mon, May 10, 2021 at 11:54:25AM +0800, Zhen Lei wrote:
>> All spelling mistakes are in the comments, no functional change.
>
> [...]
>
>> diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/mtk_iommu.c
>> index e06b8a0e2b56bdd..b9e4be35c8dcad2 100644
>> --- a/drivers/iommu/mtk_iommu.c
>> +++ b/drivers/iommu/mtk_iommu.c
>> @@ -161,7 +161,7 @@ static int mtk_iommu_hw_init(const struct mtk_iommu_data *data);
>> * The Region 'A'(I/O) can NOT be mapped by M4U; For Region 'B'/'C'/'D', the
>> * bit32 of the CPU physical address always is needed to set, and for Region
>> * 'E', the CPU physical address keep as is.
>> - * Additionally, The iommu consumers always use the CPU phyiscal address.
>> + * Additionally, The iommu consumers always use the CPU physical address.
>
> If we're fixing typos, then I think the 'T' in "The iommu" should be
> lowercase here.
OK, I will change it.
In addition, the current linux-next has several new spelling errors.
>
> Anyway, all the other fixes look correct to me. I'll leave it up to Joerg as
> to whether he wants to apply this or not, given the impact on git blame and
> the potential for conflicts.
Currently, there are no conflicts in linux-next.
>
> Will
>
> .
>
prev parent reply other threads:[~2021-06-09 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 3:54 [PATCH v2 0/1] iommu: Clear a lot of spelling mistakes Zhen Lei
2021-05-10 3:54 ` [PATCH v2 1/1] " Zhen Lei
2021-06-08 9:38 ` Will Deacon
2021-06-09 1:41 ` Leizhen (ThunderTown) [this message]
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=6c5d2840-c329-1e23-00ac-b063dd0d2b74@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-mediatek@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--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).