All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>
Cc: "Prasun.kapoor@cavium.com" <Prasun.kapoor@cavium.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	"Kumar, Vijaya" <Vijaya.Kumar@caviumnetworks.com>,
	Julien Grall <julien.grall@linaro.org>,
	Xen Devel <xen-devel@lists.xen.org>,
	Julien Grall <julien.grall@citrix.com>,
	Julien Grall <julien.grall.oss@gmail.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 15:19:25 +0100	[thread overview]
Message-ID: <1429021165.15516.67.camel@citrix.com> (raw)
In-Reply-To: <1429014241210.43895@caviumnetworks.com>

On Tue, 2015-04-14 at 12:24 +0000, Jaggi, Manish wrote:
> Hi Julien/Ian,

Please will you configure your mail client to do the chevron (">") style
of quotation favour in open source communities, picking out your replies
from the mail you are replying to is a massive chore, especially after a
couple of rounds of back and forth.

> I think a table describing the different structure would be nice.
> [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. 

Once we have a table describing the status quo then we can consider
separately whether a rename would be useful or if the documentation in
the table itself suffices.

I intend to use this table as a reference when evaluating any request to
change the names, hence I won't be considering such things until the
table exists.

Ian.

      parent reply	other threads:[~2015-04-14 14:19 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
2015-04-14 14:19                 ` Ian Campbell [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=1429021165.15516.67.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Manish.Jaggi@caviumnetworks.com \
    --cc=Prasun.kapoor@cavium.com \
    --cc=Vijaya.Kumar@caviumnetworks.com \
    --cc=julien.grall.oss@gmail.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.