From: Julien Grall <julien.grall.oss@gmail.com>
To: "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>,
Ian Campbell <ian.campbell@citrix.com>,
Julien Grall <julien.grall@citrix.com>
Cc: "Prasun.kapoor@cavium.com" <Prasun.kapoor@cavium.com>,
"Kumar, Vijaya" <Vijaya.Kumar@caviumnetworks.com>,
Julien Grall <julien.grall@linaro.org>,
Xen Devel <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v1 3/3] xen/arm: smmu: Renaming struct iommu_domain *domain to, struct iommu_domain *iommu_domain
Date: Tue, 14 Apr 2015 13:47:19 +0100 [thread overview]
Message-ID: <552D0C57.8070107@gmail.com> (raw)
In-Reply-To: <1429014241210.43895@caviumnetworks.com>
On 14/04/15 13:24, Jaggi, Manish wrote:
> [manish] Table is indeed a good option, but I think changing the name
> of arm_smmu_xen_device to something like arch_smmu_device make more
> sense as arm_smmu_xen_device and arm_smmu_device are not differentiable
> just by name.
Can you explain how arch_smmu_device and arm_smmu_device are easier to
differentiate? There is only 2 letters difference...
Also, what does "arch" stands for? The SMMU driver is already ARM
specific...
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-04-14 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 7:24 [PATCH v1 3/3] xen/arm: smmu: Renaming struct iommu_domain *domain to, struct iommu_domain *iommu_domain Manish Jaggi
2015-03-27 13:04 ` Julien Grall
2015-03-27 13:26 ` Jaggi, Manish
2015-03-27 13:41 ` Julien Grall
2015-03-27 18:05 ` Jaggi, Manish
2015-03-27 19:20 ` Julien Grall
2015-03-31 16:48 ` Stefano Stabellini
2015-04-01 8:30 ` Ian Campbell
2015-04-06 14:15 ` Julien Grall
2015-04-14 11:15 ` Ian Campbell
2015-04-14 11:46 ` Julien Grall
2015-04-14 12:24 ` Jaggi, Manish
2015-04-14 12:47 ` Julien Grall [this message]
2015-04-14 14:19 ` Ian Campbell
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=552D0C57.8070107@gmail.com \
--to=julien.grall.oss@gmail.com \
--cc=Manish.Jaggi@caviumnetworks.com \
--cc=Prasun.kapoor@cavium.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@citrix.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.