All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tamas K Lengyel <tamas@tklengyel.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Artem Mygaiev <Artem_Mygaiev@epam.com>,
	Lars Kurth <lars.kurth@citrix.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>,
	Iurii Artemenko <Iurii_Artemenko@epam.com>,
	Jan Beulich <jbeulich@suse.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [RFC] xen: Add .astylerc for automated style-formatting
Date: Thu, 18 Jul 2019 11:22:00 -0600	[thread overview]
Message-ID: <CABfawhnk+_ssU1xEzN6O+_JkH4jT2NguP30VRpkNKzc7xoKeXw@mail.gmail.com> (raw)
In-Reply-To: <fcbf4968-7b82-6e5d-75ae-e4c2ff059b4d@arm.com>

>    - Line 139: The { are commonly on the same line as struct or definition.

According to CODING_STYLE that's not how it should be.

Tamas

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

  parent reply	other threads:[~2019-07-18 17:23 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 14:43 [Xen-devel] [RFC] xen: Add .astylerc for automated style-formatting Tamas K Lengyel
2019-07-18 15:02 ` Julien Grall
2019-07-18 15:14   ` Tamas K Lengyel
2019-07-18 15:42     ` Julien Grall
2019-07-18 17:18       ` Tamas K Lengyel
2019-07-19  8:26         ` Julien Grall
2019-07-18 17:22       ` Tamas K Lengyel [this message]
2019-07-19  8:35         ` Julien Grall
2019-07-26 14:58           ` Viktor Mitin
2019-07-26 15:12             ` Julien Grall
2019-07-26 15:23               ` Tamas K Lengyel
2019-07-29  7:31               ` Lars Kurth
2019-07-19  9:00         ` Jan Beulich
2019-07-19 13:10           ` Tamas K Lengyel
2019-07-26 14:52         ` Viktor Mitin
2019-07-18 17:25       ` Tamas K Lengyel
2019-07-18 17:32       ` Tamas K Lengyel
2019-07-18 17:38       ` Tamas K Lengyel
2019-07-18 17:48       ` Tamas K Lengyel
2019-07-19  8:43         ` Julien Grall
2019-07-19 13:00           ` Tamas K Lengyel
2019-07-19 13:11             ` Julien Grall
2019-07-19 13:14               ` Tamas K Lengyel
2019-07-19 13:24                 ` Julien Grall
2019-07-19 13:31                   ` Julien Grall
2019-07-19 13:50                     ` Rich Persaud
2019-07-19 14:47                       ` Julien Grall
2019-07-24 12:53                       ` Lars Kurth
2019-07-19 13:52                     ` Tamas K Lengyel
2019-07-26 14:54         ` Viktor Mitin
2019-07-26 14:49       ` Viktor Mitin
2019-07-26 14:57         ` Julien Grall
2019-07-29 12:19         ` Jan Beulich
2019-07-29 12:49           ` Julien Grall
2019-07-29 13:02             ` Jan Beulich
2019-07-31 16:20               ` Viktor Mitin
2019-08-01  7:37                 ` Jan Beulich
2019-08-01 12:16                   ` Viktor Mitin
2019-08-01 12:43                     ` Jan Beulich
2019-08-01 12:50                     ` Juergen Gross
2019-08-02  8:38                       ` Viktor Mitin
2019-08-02  9:23                         ` Juergen Gross
2019-08-02 11:44                           ` Viktor Mitin
2019-08-02 12:57                             ` Jan Beulich
2019-07-18 15:13 ` Jan Beulich
2019-07-18 15:16   ` Tamas K Lengyel
2019-07-26 14:42   ` Viktor Mitin
2019-07-26 14:50     ` Tamas K Lengyel
2019-07-18 17:58 ` Andrew Cooper
2019-07-18 18:34   ` Tamas K Lengyel
2019-07-19  9:03     ` Julien Grall
2019-07-19 13:05       ` Tamas K Lengyel
2019-07-19 13:34         ` Julien Grall
2019-07-19 13:36           ` Tamas K Lengyel
2019-07-19 13:26 ` Rich Persaud
2019-07-26 15:48 ` Viktor Mitin
2019-07-26 15:54   ` Julien Grall
2019-07-29  7:20     ` Viktor Mitin

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=CABfawhnk+_ssU1xEzN6O+_JkH4jT2NguP30VRpkNKzc7xoKeXw@mail.gmail.com \
    --to=tamas@tklengyel.com \
    --cc=Artem_Mygaiev@epam.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Iurii_Artemenko@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lars.kurth@citrix.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.