From: Ian Campbell <Ian.Campbell@citrix.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>
Cc: Keir Fraser <keir@xen.org>,
George Dunlap <george.dunlap@eu.citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] numa.c: use spaces instead of tabs
Date: Wed, 3 Sep 2014 13:18:12 +0100 [thread overview]
Message-ID: <1409746692.20794.14.camel@citrix.com> (raw)
In-Reply-To: <CAEr7rXiJvu6Dr=w7SE_=usC+jp36Cr2jfarUZWqrfuteTrM4PQ@mail.gmail.com>
On Wed, 2014-09-03 at 07:59 -0400, Elena Ufimtseva wrote:
> On Wed, Sep 3, 2014 at 6:01 AM, Jan Beulich <JBeulich@suse.com> wrote:
> >>>> On 03.09.14 at 11:52, <dario.faggioli@citrix.com> wrote:
> >> On mer, 2014-09-03 at 00:18 -0400, Elena Ufimtseva wrote:
> >>> Signed-off-by: Elena Ufimtseva <ufimtseva@gmail.com>
> >>> ---
> >>>
> >> I think the patch does what the subject says, i.e., converting tabs to
> >> spaces, and does it right (I've only one question, see below).
> >>
> >> However, does it make sense, while at it, to turn the file into a Xen's
> >> code stile compliant one? Because, if yes, there are other things than
> >> tabs-->spaces that needs fixing, I believe.
> >
> > Yes, indeed - we don't use a style like what results from this patch.
> >
> >>> @@ -121,83 +121,83 @@ static int __init
> >> allocate_cachealigned_memnodemap(void)
> >>> * maximum possible shift.
> >>> */
> >>> static int __init extract_lsb_from_nodes(const struct node *nodes,
> >>> - int numnodes)
> >>> + int numnodes)
> >>>
> >> Perhaps I am the one missing something here, but shouldn't this still be
> >> aligned to the '(' above (through spaces, of course)?
> >
> > Indeed it should.
> >
> > Jan
> >
>
>
> Dario, Jan
>
> True to that there are few other things that should be fixed in
> regards to the style.
>
> But about the tabs/spaces what patch attempt to change, as it says.
>
> Jan, you say that such style is not used.. But numa.c uses tabs as
> :set list shows and its not Xen style either.
> Coding style says - 4 spaces for one level of indent. numa.c uses tabs
> and sometimes space between tabs.
>
> I am looking at the rest of the files in xen/arch/x86/ and see that
> they have all same tab= 4 spaces for indentation.
> for example see xen/arch/x86/domain.c.
> I used this for vim to re-tab the file: set noai ts=4 sw=8 expandtab
I think what Jan meant was that simply changing tabs->spaces did not
result in any valid coding style, since Xen style differs from the
result in other ways too (e.g. spacing inside the spaces surrounding
expressions).
> Linux has 8 spaces for tabs.. So I am lost here.
Was numa.c imported from Linux? In such cases we often (try to) stick
with Linux style.
Ian.
next prev parent reply other threads:[~2014-09-03 12:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 4:18 [PATCH] numa.c: use spaces instead of tabs Elena Ufimtseva
2014-09-03 9:52 ` Dario Faggioli
2014-09-03 10:01 ` Jan Beulich
2014-09-03 11:59 ` Elena Ufimtseva
2014-09-03 12:18 ` Ian Campbell [this message]
2014-09-03 12:29 ` Elena Ufimtseva
2014-09-03 12:29 ` Jan Beulich
2014-09-03 12:34 ` Elena Ufimtseva
2014-09-03 12:40 ` Jan Beulich
2014-09-06 17:28 ` Don Slutz
2014-09-08 6:53 ` Jan Beulich
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=1409746692.20794.14.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=ufimtseva@gmail.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 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).