From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Yong Wu <yong.wu@mediatek.com>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
iommu@lists.linux.dev, linux-mediatek@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mingyuan.ma@mediatek.com,
yf.wang@mediatek.com, jianjiao.zeng@mediatek.com,
chengci.xu@mediatek.com
Subject: Re: [PATCH v10 7/7] MAINTAINERS: iommu/mediatek: Update the header file name
Date: Mon, 17 Apr 2023 11:04:03 +0200 [thread overview]
Message-ID: <b645c058-9f51-034b-0e81-94c8d69469c1@collabora.com> (raw)
In-Reply-To: <20230417073606.25729-8-yong.wu@mediatek.com>
Il 17/04/23 09:36, Yong Wu ha scritto:
> We add the prefix "mediatek," for the lastest ports header file name,
> For example, include/dt-bindings/memory/mediatek,mt8188-memory-port.h.
> Update the entry from "mt*" to "m*".
>
> Signed-off-by: Yong Wu <yong.wu@mediatek.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d8ebab595b2a..833d32c356ef 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13056,7 +13056,7 @@ L: linux-mediatek@lists.infradead.org (moderated for non-subscribers)
> S: Supported
> F: Documentation/devicetree/bindings/iommu/mediatek*
> F: drivers/iommu/mtk_iommu*
> -F: include/dt-bindings/memory/mt*-port.h
> +F: include/dt-bindings/memory/m*-port.h
Stuff that's not MediaTek specific which filename starts by m and ends for -port.h
is really unlikely, but we can prevent future issues.
Perhaps the best idea here would be to keep the mt*-port.h and add a new file entry
with mediatek,mt*-port.h.
Regards,
Angelo
prev parent reply other threads:[~2023-04-17 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 7:35 [PATCH v10 0/7] MT8188 IOMMU SUPPORT Yong Wu
2023-04-17 7:36 ` [PATCH v10 1/7] dt-bindings: mediatek: mt8188: Add binding for MM & INFRA IOMMU Yong Wu
2023-04-17 7:36 ` [PATCH v10 2/7] iommu/mediatek: Fix two IOMMU share pagetable issue Yong Wu
2023-04-17 9:00 ` AngeloGioacchino Del Regno
2023-04-17 7:36 ` [PATCH v10 3/7] iommu/mediatek: Adjust mtk_iommu_config flow Yong Wu
2023-04-17 7:36 ` [PATCH v10 4/7] iommu/mediatek: Add enable IOMMU SMC command for INFRA masters Yong Wu
2023-04-17 7:36 ` [PATCH v10 5/7] iommu/mediatek: Add MT8188 IOMMU Support Yong Wu
2023-04-17 7:36 ` [PATCH v10 6/7] iommu/mediatek: mt8188: Add iova_region_larb_msk Yong Wu
2023-04-17 7:36 ` [PATCH v10 7/7] MAINTAINERS: iommu/mediatek: Update the header file name Yong Wu
2023-04-17 9:04 ` AngeloGioacchino Del Regno [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=b645c058-9f51-034b-0e81-94c8d69469c1@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=chengci.xu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jianjiao.zeng@mediatek.com \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski+dt@linaro.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=mingyuan.ma@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yf.wang@mediatek.com \
--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).