All of lore.kernel.org
 help / color / mirror / Atom feed
From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
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>,
	Jan Beulich <jbeulich@suse.com>,
	"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, 24 Sep 2019 15:37:09 +0000	[thread overview]
Message-ID: <875zlhaeoq.fsf@epam.com> (raw)
In-Reply-To: <ca85e985-e40e-e701-6fc4-efc541f2f00f@arm.com>


Julien Grall writes:

> Hi,
>
> On 9/24/19 3:56 PM, Volodymyr Babchuk wrote:
>> Julien Grall writes:
>>
>>> The documentation is using a mix of ARM (old) and Arm (new). To stay
>>> consistent, use only the new name.
>>>
>> Honestly, this rename confuses me. I think, this commit is the good
>> place to clarify a couple of questions.
>
> It did confuse a lot when the rename was made by Arm... What I want to
> avoid is mixing the both in the documentation as this makes things
> more difficult to follow.
>
> There are probably more to tidy up, but then you have to start somewhere.

Thank you for explanation. Just in case: I have nothing against this
particular patch. I just wanted to understand how to use this names
correctly.

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

  reply	other threads:[~2019-09-24 15:37 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 [this message]
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
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=875zlhaeoq.fsf@epam.com \
    --to=volodymyr_babchuk@epam.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --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.