From: "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>
To: Julien Grall <julien.grall@linaro.org>,
Xen Devel <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"Prasun.kapoor@cavium.com" <Prasun.kapoor@cavium.com>,
"Kumar, Vijaya" <Vijaya.Kumar@caviumnetworks.com>
Subject: Re: [PATCH v1 1/3] xen/arm: smmu: Rename arm_smmu_xen_device with, device_iommu_info
Date: Fri, 27 Mar 2015 18:00:55 +0000 [thread overview]
Message-ID: <1427479254399.31116@caviumnetworks.com> (raw)
In-Reply-To: <55155CA0.5010304@linaro.org>
________________________________
From: Julien Grall <julien.grall@linaro.org>
Sent: Friday, March 27, 2015 7:05 PM
To: Jaggi, Manish; Xen Devel; Stefano Stabellini; Ian Campbell; Prasun.kapoor@cavium.com; Kumar, Vijaya
Subject: Re: [PATCH v1 1/3] xen/arm: smmu: Rename arm_smmu_xen_device with, device_iommu_info
On 27/03/15 13:21, Jaggi, Manish wrote:
>
>
> Regards,
> Manish Jaggi
Could you please try to configure you email client correctly? It's
rather confusing the "regards, Manish Jaggi" at the beginning of the mail.
[manish] Fixed. Thanks for pointing out
> ________________________________________
> From: Julien Grall <julien.grall@linaro.org>
> Sent: Friday, March 27, 2015 6:29 PM
> To: Jaggi, Manish; Xen Devel; Stefano Stabellini; Ian Campbell; Prasun.kapoor@cavium.com; Kumar, Vijaya
> Subject: Re: [PATCH v1 1/3] xen/arm: smmu: Rename arm_smmu_xen_device with, device_iommu_info
>
> Hi Manish,
>
> On 27/03/15 07:20, Manish Jaggi wrote:
>> arm_smmu_xen_device is not an intuitive name for a datastructure which
>> represents
>> device->archdata.iommu. Rename arm_smmu_xen_device with device_iommu_info
>
> device_iommu_info is not more intuitive... At least arm_smmu_xen_device
> shows that it's a specific Xen structure and not coming from the Linux
> drivers.
>
> [manish] But that is not a valid reason for a non intuitive naming. It is really hard to keep us readability of the code with arm_smmu_xen_device. It is not clear that it is referring to a device attached to smmu or smmu itself. There is another data structure arm_smmu_device as well.
Did you read the comment explaining the structure arm_smmu_xen_device?
It's just above the definition.
"arm_smmu" is the prefix for any structure within this file.
"xen" means it's a structure added for Xen.
"device" means it's data stored for a device.
> Please choose another name I can take it but arm_smmu_xen_device is really confusing
I won't choose a name myself for a name that I think valid...
If you really want to change the name, you have to put at least
arm_smmu_xen_ in the name.
[manish] what about device_archdata_priv, this is denoting what it is.
> Regards,
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-03-27 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 7:20 [PATCH v1 1/3] xen/arm: smmu: Rename arm_smmu_xen_device with, device_iommu_info Manish Jaggi
2015-03-27 12:59 ` Julien Grall
2015-03-27 13:21 ` Jaggi, Manish
2015-03-27 13:35 ` Julien Grall
2015-03-27 18:00 ` Jaggi, Manish [this message]
2015-04-06 10:45 ` Manish Jaggi
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=1427479254399.31116@caviumnetworks.com \
--to=manish.jaggi@caviumnetworks.com \
--cc=Ian.Campbell@citrix.com \
--cc=Prasun.kapoor@cavium.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.