All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Julien Grall <julien.grall@arm.com>
Cc: "jgross@suse.com" <jgross@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [PATCH for-4.13 v2 2/2] docs: Replace all instance of ARM by Arm
Date: Tue, 15 Oct 2019 09:47:04 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1910150947000.30080@sstabellini-ThinkPad-T480s> (raw)
In-Reply-To: <5ba2ce4b-4fa4-9650-7428-ee09f27dbff0@arm.com>

[-- Attachment #1: Type: text/plain, Size: 2977 bytes --]

I am OK switching to "Arm", however I would do it post-4.13: this is not
the kind of thing we should worry about it now I think.

On Tue, 15 Oct 2019, Julien Grall wrote:
> Hi,
> 
> Gentle, ping. I don't think there are any conclusion here.
> 
> Should we stick to ARM or move to Arm?
> 
> Cheers,
> 
> On 10/3/19 5:02 PM, Julien Grall wrote:
> > Hi,
> > 
> > On 03/10/2019 16:55, Volodymyr Babchuk wrote:
> > > Julien Grall writes:
> > > 
> > > > Hi Stefano,
> > > > 
> > > > On 10/2/19 2:05 AM, Stefano Stabellini wrote:
> > > > > On Tue, 24 Sep 2019, Julien Grall wrote:
> > > > > > The documentation is using a mix of ARM (old) and Arm (new). To stay
> > > > > > consistent, use only the new name.
> > > > > 
> > > > > Thank you for the patch, it must have been "not fun" to write this
> > > > > patch.
> > > > > 
> > > > > However, let me suggest a radical maybe controversial idea. What about
> > > > > keeping "ARM" instead of switching? There are several advantages: it
> > > > > is
> > > > > easier to grep, no need to worry about case-sensitivity. It is what
> > > > > people are used to, and what still use (in my experience at conference
> > > > > and at work.) Would it make sense to ignore Arm's marketing and keep
> > > > > the
> > > > > old "ARM" nomenclature?
> > > > 
> > > > Pretty much all the new documentation on Arm website are now using Arm
> > > > (the spec is now called Arm Arm).
> > > This confuses me, because I believed that second "Arm" stands for
> > > Architecture Reference Manual.
> > Sorry it is Arm ARM. But they tend to use the longer name Arm Architecture
> > Reference Manual.
> > 
> > > 
> > > > > 
> > > > > If not, I'd suggest to also replace "arm" with "Arm" so that at least
> > > > > with have consistent cases everywhere. But then the pathnames would
> > > > > remain xen/arch/arm, leading to sentences such as:
> > > > > 
> > > > >    (non-zImage)" protocol described in arm/Booting.
> > > > >       There are no exception on 64-bit Arm.
> > > > > 
> > > > > With "arm" and "ARM" the distinction was clear between pathnames and
> > > > > text (at least to me.) With "arm" and "Arm", I know it is silly but it
> > > > > kind of bothers me :-)
> > > > 
> > > > How do you deal with Xilinx then? ;)
> > > > 
> > > > > 
> > > > > I am not going to insist on this one though.
> > > > 
> > > > This is quite similar to a company renaming itself (or got acquired
> > > > and the name completely disappear) but in a less radical way. Would
> > > > you still keep the old name company in your documentation and/or
> > > > mixing the both?
> > > BTW, this if what happened with Freescale/NXP. Linux and U-Boot still
> > > use "freescale" even for i.MX8 chips.
> > 
> > Maybe because nobody bothered to do it? I would like some consistency in the
> > documentation and hence using the new name makes sense. But I am not
> > bothered enough to argue whether we should stay in the past.
> > 
> > Cheers,
> > 
> 
> -- 
> Julien Grall
> 

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-10-15 16:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 14:35 [Xen-devel] [PATCH for-4.13 v2 0/2] Errata implementation and doc update Julien Grall
2019-09-24 14:35 ` [Xen-devel] [PATCH for-4.13 v2 1/2] xen/arm: Implement workaround for Cortex A-57 and Cortex A72 AT speculate Julien Grall
2019-10-02  0:56   ` Stefano Stabellini
2019-09-24 14:35 ` [Xen-devel] [PATCH for-4.13 v2 2/2] docs: Replace all instance of ARM by Arm Julien Grall
2019-09-24 14:56   ` Volodymyr Babchuk
2019-09-24 15:28     ` Julien Grall
2019-09-24 15:37       ` Volodymyr Babchuk
2019-09-24 15:38         ` Julien Grall
2019-10-02  1:05   ` Stefano Stabellini
2019-10-02  8:49     ` Julien Grall
2019-10-03 15:55       ` Volodymyr Babchuk
2019-10-03 16:02         ` Julien Grall
2019-10-15 16:42           ` Julien Grall
2019-10-15 16:47             ` Stefano Stabellini [this message]
2019-10-15 16:52               ` Julien Grall
2019-09-24 14:43 ` [Xen-devel] [PATCH for-4.13 v2 0/2] Errata implementation and doc update Jürgen Groß
2019-09-24 14:51 ` Wei Liu

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=alpine.DEB.2.21.1910150947000.30080@sstabellini-ThinkPad-T480s \
    --to=sstabellini@kernel.org \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=tim@xen.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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.