From: Nicolin Chen <nicoleotsuka@gmail.com> To: Thierry Reding <thierry.reding@gmail.com> Cc: joro@8bytes.org, will@kernel.org, vdumpa@nvidia.com, jonathanh@nvidia.com, linux-tegra@vger.kernel.org, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, digetx@gmail.com Subject: Re: [PATCH v6 3/6] iommu/tegra-smmu: Rename struct tegra_smmu_swgroup *group to *swgrp Date: Thu, 7 Oct 2021 13:29:45 -0700 [thread overview] Message-ID: <20211007202945.GB20821@Asurada-Nvidia> (raw) In-Reply-To: <YV8m+0qP2ibQBvNs@orome.fritz.box> On Thu, Oct 07, 2021 at 06:57:31PM +0200, Thierry Reding wrote: > On Mon, Sep 13, 2021 at 06:38:55PM -0700, Nicolin Chen wrote: > > There are both tegra_smmu_swgroup and tegra_smmu_group structs > > using "group" for their pointer instances. This gets confusing > > to read the driver sometimes. > > > > So this patch renames "group" of struct tegra_smmu_swgroup to > > "swgrp" as a cleanup. Also renames its "find" function. > > > > Note that we already have "swgroup" being used for an unsigned > > int type variable that is inside struct tegra_smmu_swgroup, so > > it's not able to use "swgroup" but only something like "swgrp". > > > > Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com> > > --- > > drivers/iommu/tegra-smmu.c | 34 +++++++++++++++++----------------- > > 1 file changed, 17 insertions(+), 17 deletions(-) > > > > diff --git a/drivers/iommu/tegra-smmu.c b/drivers/iommu/tegra-smmu.c > > index a32ed347e25d..0f3883045ffa 100644 > > --- a/drivers/iommu/tegra-smmu.c > > +++ b/drivers/iommu/tegra-smmu.c > > @@ -334,35 +334,35 @@ static void tegra_smmu_domain_free(struct iommu_domain *domain) > > } > > > > static const struct tegra_smmu_swgroup * > > -tegra_smmu_find_swgroup(struct tegra_smmu *smmu, unsigned int swgroup) > > +tegra_smmu_find_swgrp(struct tegra_smmu *smmu, unsigned int swgroup) > > This makes things inconsistent now. The tegra_smmu_find_swgroup() name > indicates that we're looking for some "swgroup" entity within an "smmu" > object. The entity that we're looking for is a struct tegra_smmu_swgroup > so I think it makes sense to use that full name in the function name. This is more like an indirect change to keep consistency between function name and pointer name. > > { > > - const struct tegra_smmu_swgroup *group = NULL; > > + const struct tegra_smmu_swgroup *swgrp = NULL; > > I don't think the existing naming is confusing. The variable name > "group" is consistently used for tegra_smmu_swgroup structures and there > are no cases where we would confuse them with struct tegra_smmu_group > instances. If we don't rename it, then PATCH-4 adds to struct tegra_smmu_group a "struct tegra_smmu_swgroup *group", which results in a confusing group->group... > However, I don't feel strongly about it, so I'm fine with changing the > variable names to "swgrp" if you think that makes things less confusing. Yea, I'd like to keep this change. I will respin it in next version after fixing other comments.
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com> To: Thierry Reding <thierry.reding@gmail.com> Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, jonathanh@nvidia.com, linux-tegra@vger.kernel.org, digetx@gmail.com, will@kernel.org Subject: Re: [PATCH v6 3/6] iommu/tegra-smmu: Rename struct tegra_smmu_swgroup *group to *swgrp Date: Thu, 7 Oct 2021 13:29:45 -0700 [thread overview] Message-ID: <20211007202945.GB20821@Asurada-Nvidia> (raw) In-Reply-To: <YV8m+0qP2ibQBvNs@orome.fritz.box> On Thu, Oct 07, 2021 at 06:57:31PM +0200, Thierry Reding wrote: > On Mon, Sep 13, 2021 at 06:38:55PM -0700, Nicolin Chen wrote: > > There are both tegra_smmu_swgroup and tegra_smmu_group structs > > using "group" for their pointer instances. This gets confusing > > to read the driver sometimes. > > > > So this patch renames "group" of struct tegra_smmu_swgroup to > > "swgrp" as a cleanup. Also renames its "find" function. > > > > Note that we already have "swgroup" being used for an unsigned > > int type variable that is inside struct tegra_smmu_swgroup, so > > it's not able to use "swgroup" but only something like "swgrp". > > > > Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com> > > --- > > drivers/iommu/tegra-smmu.c | 34 +++++++++++++++++----------------- > > 1 file changed, 17 insertions(+), 17 deletions(-) > > > > diff --git a/drivers/iommu/tegra-smmu.c b/drivers/iommu/tegra-smmu.c > > index a32ed347e25d..0f3883045ffa 100644 > > --- a/drivers/iommu/tegra-smmu.c > > +++ b/drivers/iommu/tegra-smmu.c > > @@ -334,35 +334,35 @@ static void tegra_smmu_domain_free(struct iommu_domain *domain) > > } > > > > static const struct tegra_smmu_swgroup * > > -tegra_smmu_find_swgroup(struct tegra_smmu *smmu, unsigned int swgroup) > > +tegra_smmu_find_swgrp(struct tegra_smmu *smmu, unsigned int swgroup) > > This makes things inconsistent now. The tegra_smmu_find_swgroup() name > indicates that we're looking for some "swgroup" entity within an "smmu" > object. The entity that we're looking for is a struct tegra_smmu_swgroup > so I think it makes sense to use that full name in the function name. This is more like an indirect change to keep consistency between function name and pointer name. > > { > > - const struct tegra_smmu_swgroup *group = NULL; > > + const struct tegra_smmu_swgroup *swgrp = NULL; > > I don't think the existing naming is confusing. The variable name > "group" is consistently used for tegra_smmu_swgroup structures and there > are no cases where we would confuse them with struct tegra_smmu_group > instances. If we don't rename it, then PATCH-4 adds to struct tegra_smmu_group a "struct tegra_smmu_swgroup *group", which results in a confusing group->group... > However, I don't feel strongly about it, so I'm fine with changing the > variable names to "swgrp" if you think that makes things less confusing. Yea, I'd like to keep this change. I will respin it in next version after fixing other comments. _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-10-07 20:37 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-14 1:38 [PATCH v6 0/6] iommu/tegra-smmu: Add pagetable mappings to debugfs Nicolin Chen 2021-09-14 1:38 ` Nicolin Chen 2021-09-14 1:38 ` [PATCH v6 1/6] iommu/tegra-smmu: Rename struct iommu_group *group to *grp Nicolin Chen 2021-09-14 1:38 ` Nicolin Chen 2021-10-07 16:43 ` Thierry Reding 2021-10-07 16:43 ` Thierry Reding 2021-09-14 1:38 ` [PATCH v6 2/6] iommu/tegra-smmu: Rename struct tegra_smmu_group_soc *soc to *group_soc Nicolin Chen 2021-09-14 1:38 ` Nicolin Chen 2021-10-07 16:50 ` Thierry Reding 2021-10-07 16:50 ` Thierry Reding 2021-10-07 20:14 ` Nicolin Chen 2021-10-07 20:14 ` Nicolin Chen 2021-09-14 1:38 ` [PATCH v6 3/6] iommu/tegra-smmu: Rename struct tegra_smmu_swgroup *group to *swgrp Nicolin Chen 2021-09-14 1:38 ` Nicolin Chen 2021-10-07 16:57 ` Thierry Reding 2021-10-07 16:57 ` Thierry Reding 2021-10-07 20:29 ` Nicolin Chen [this message] 2021-10-07 20:29 ` Nicolin Chen 2021-09-14 1:38 ` [PATCH v6 4/6] iommu/tegra-smmu: Use swgrp pointer instead of swgroup id Nicolin Chen 2021-09-14 1:38 ` Nicolin Chen 2021-10-07 16:59 ` Thierry Reding 2021-10-07 16:59 ` Thierry Reding 2021-09-14 1:38 ` [PATCH v6 5/6] iommu/tegra-smmu: Attach as pointer to tegra_smmu_group Nicolin Chen 2021-09-14 1:38 ` Nicolin Chen 2021-10-07 17:02 ` Thierry Reding 2021-10-07 17:02 ` Thierry Reding 2021-09-14 1:38 ` [PATCH v6 6/6] iommu/tegra-smmu: Add pagetable mappings to debugfs Nicolin Chen 2021-09-14 1:38 ` Nicolin Chen 2021-09-14 13:29 ` Dmitry Osipenko 2021-09-14 13:29 ` Dmitry Osipenko 2021-09-14 18:49 ` Nicolin Chen 2021-09-14 18:49 ` Nicolin Chen 2021-09-14 19:20 ` Dmitry Osipenko 2021-09-14 19:20 ` Dmitry Osipenko 2021-09-15 4:38 ` Nicolin Chen 2021-09-15 4:38 ` Nicolin Chen 2021-09-15 12:09 ` Dmitry Osipenko 2021-09-15 12:09 ` Dmitry Osipenko 2021-09-15 12:18 ` Dmitry Osipenko 2021-09-15 12:18 ` Dmitry Osipenko 2021-09-15 22:19 ` Nicolin Chen 2021-09-15 22:19 ` Nicolin Chen 2021-10-07 17:13 ` Thierry Reding 2021-10-07 17:13 ` Thierry Reding 2021-10-07 20:41 ` Nicolin Chen 2021-10-07 20:41 ` Nicolin Chen
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=20211007202945.GB20821@Asurada-Nvidia \ --to=nicoleotsuka@gmail.com \ --cc=digetx@gmail.com \ --cc=iommu@lists.linux-foundation.org \ --cc=jonathanh@nvidia.com \ --cc=joro@8bytes.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=thierry.reding@gmail.com \ --cc=vdumpa@nvidia.com \ --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: linkBe 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.