qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: clg@kaod.org, groug@kaod.org, agraf@suse.de, lvivier@redhat.com,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Use CamelCase properly
Date: Fri, 8 Mar 2019 11:14:43 +1100	[thread overview]
Message-ID: <20190308001443.GG7722@umbus.fritz.box> (raw)
In-Reply-To: <ad194b40-507d-5de1-dc1c-23adb046fac7@ozlabs.ru>

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

On Thu, Mar 07, 2019 at 04:38:28PM +1100, Alexey Kardashevskiy wrote:
> 
> 
> On 07/03/2019 16:21, David Gibson wrote:
> > The qemu coding standard is to use CamelCase for type and structure names,
> > and the pseries code follows that... sort of.  There are quite a lot of
> > places where we bend the rules in order to preserve the capitalization of
> > internal acronyms like "PHB", "TCE", "DIMM" and most commonly "sPAPR".
> > 
> > That was a bad idea - it frequently leads to names ending up with hard to
> > read clusters of capital letters, and means they don't catch the eye as
> > type identifiers, which is kind of the point of the CamelCase convention in
> > the first place.
> > 
> > In short, keeping type identifiers look like CamelCase is more important
> > than preserving standard capitalization of internal "words".  So, this
> > patch renames a heap of spapr internal type names to a more standard
> > CamelCase.
> > 
> > In addition to case changes, we also make some other identifier renames:
> >   VIOsPAPR* -> SpaprVio*
> >     The reverse word ordering was only ever used to mitigate the capital
> >     cluster, so revert to the natural ordering.
> >   VIOsPAPRVTYDevice -> SpaprVioVty
> >   VIOsPAPRVLANDevice -> SpaprVioVlan
> >     Brevity, since the "Device" didn't add useful information
> >   sPAPRDRConnector -> SpaprDrc
> >   sPAPRDRConnectorClass -> SpaprDrcClass
> >     Brevity, and makes it clearer this is the same thing as a "DRC"
> >     mentioned in many other places in the code
> > 
> > This is 100% a mechanical search-and-replace patch. It will, however,
> > conflict with essentially any and all outstanding patches touching the
> > spapr code.
> 
> 
> so it would be nice to have the script to fix those outstanding patches
> before reposting.

Sorry, I don't have a script for this.

The patch is equivalent to a scripted replacement, but I didn't
actually make it with a script - I built it up interactively using the
"regexxer" tool.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2019-03-08  1:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  5:21 [Qemu-devel] [PATCH] spapr: Use CamelCase properly David Gibson
2019-03-07  5:38 ` Alexey Kardashevskiy
2019-03-07 10:34   ` Philippe Mathieu-Daudé
2019-03-08  0:14   ` David Gibson [this message]
2019-03-11  9:48 ` Greg Kurz

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=20190308001443.GG7722@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=clg@kaod.org \
    --cc=groug@kaod.org \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).