From: Lars Kurth <lars.kurth@citrix.com>
To: Iurii Artemenko <Iurii_Artemenko@epam.com>,
Juergen Gross <jgross@suse.com>
Cc: Artem Mygaiev <Artem_Mygaiev@epam.com>,
Wei Liu <wei.liu2@citrix.com>,
Lars Kurth <lars.kurth.xen@gmail.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
cardoe <cardoe@cardoe.com>,
Andrii Anisov <Andrii_Anisov@epam.com>,
'Jan Beulich' <JBeulich@suse.com>,
Ian Jackson <Ian.Jackson@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen checkpatch infrastructure design
Date: Wed, 26 Jul 2017 16:50:35 +0000 [thread overview]
Message-ID: <D59E85CB.39836%lars.kurth@citrix.com> (raw)
In-Reply-To: <DB6PR03MB3000EB938C08C47976D9F052FDB90@DB6PR03MB3000.eurprd03.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 2302 bytes --]
> We did not plan any changes into the clang-format yet. We have to check with Artem our next steps.
I don't think this is a huge task. I think it is also something that is important enough for the Advisory Board to make funds available – assuming this can't be done otherwise (but I can't promise it would be approved and going this route will take fairly long and would require quite a bit of paperwork)
> Artem is on vacations now.
Let me know when you talked to Artem
Lars
From: Iurii Artemenko <Iurii_Artemenko@epam.com<mailto:Iurii_Artemenko@epam.com>>
Date: Wednesday, 26 July 2017 at 17:08
To: Lars Kurth <lars.kurth@citrix.com<mailto:lars.kurth@citrix.com>>, Juergen Gross <jgross@suse.com<mailto:jgross@suse.com>>
Cc: Wei Liu <wei.liu2@citrix.com<mailto:wei.liu2@citrix.com>>, Andrew Cooper <Andrew.Cooper3@citrix.com<mailto:Andrew.Cooper3@citrix.com>>, Ian Jackson <Ian.Jackson@citrix.com<mailto:Ian.Jackson@citrix.com>>, 'Jan Beulich' <JBeulich@suse.com<mailto:JBeulich@suse.com>>, xen-devel <xen-devel@lists.xenproject.org<mailto:xen-devel@lists.xenproject.org>>, cardoe <cardoe@cardoe.com<mailto:cardoe@cardoe.com>>, Andrii Anisov <Andrii_Anisov@epam.com<mailto:Andrii_Anisov@epam.com>>, Lars Kurth <lars.kurth.xen@gmail.com<mailto:lars.kurth.xen@gmail.com>>, Artem Mygaiev <Artem_Mygaiev@epam.com<mailto:Artem_Mygaiev@epam.com>>
Subject: Re: [Xen-devel] Xen checkpatch infrastructure design
Hi Lars,
> I was wondering how you deal with the gaps. I suppose these gaps could possibly be covered in clang-format-diff.py
> Of course this info may be out-of-date
I assumed that everything is fine with clang-format and started with python script.
Now I have checked both clang-format-3.9 and 5.0, all of those gaps are still remaining.
Also there are no corespondent changes expected in Clang-6.0 which currently in-progress.
> I wanted to double check, as we had previously looked into clang-format, and it showed some gaps with what it can be used for in Xen coding styles. Which is why we tried to get > agreement - > and got it - to upstream Xen related changes into clang–format
We did not plan any changes into the clang-format yet. We have to check with Artem our next steps.
Artem is on vacations now.
Regards
Iurii
[-- Attachment #1.2: Type: text/html, Size: 6388 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-26 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 8:50 Xen checkpatch infrastructure design Juergen Gross
2017-07-24 11:44 ` Lars Kurth
2017-07-24 12:46 ` Andrii Anisov
2017-07-24 16:55 ` Iurii Artemenko
2017-07-24 17:35 ` Lars Kurth
2017-07-26 16:08 ` Iurii Artemenko
2017-07-26 16:50 ` Lars Kurth [this message]
2017-07-24 18:08 ` Juergen Gross
2017-07-26 15:36 ` Iurii Artemenko
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=D59E85CB.39836%lars.kurth@citrix.com \
--to=lars.kurth@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Andrii_Anisov@epam.com \
--cc=Artem_Mygaiev@epam.com \
--cc=Ian.Jackson@citrix.com \
--cc=Iurii_Artemenko@epam.com \
--cc=JBeulich@suse.com \
--cc=cardoe@cardoe.com \
--cc=jgross@suse.com \
--cc=lars.kurth.xen@gmail.com \
--cc=wei.liu2@citrix.com \
--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.