From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Grygorii Strashko <grygorii_strashko@epam.com>
Cc: Oleksandr Andrushchenko <andr2000@gmail.com>,
xen-devel@lists.xenproject.org, sstabellini@kernel.org,
Artem_Mygaiev@epam.com, jbeulich@suse.com, Luca.Fancellu@arm.com,
marmarek@invisiblethingslab.com, andrew.cooper3@citrix.com,
anthony.perard@vates.tech
Subject: Re: [PATCH 0/2] code style exercise: Drivers folder samples
Date: Tue, 18 Feb 2025 12:41:01 +0100 [thread overview]
Message-ID: <Z7RxzdK9wJy5K_c4@macbook.local> (raw)
In-Reply-To: <6c25b6fb-989c-4788-9f3f-c2e309bec4ba@epam.com>
On Tue, Feb 18, 2025 at 11:56:48AM +0200, Grygorii Strashko wrote:
> Honestly, It looks a bit strange that Xen community is considering batch automated code formatting,
> For example Linux kernel cleanly rejected such approach.
> Linux kernel docs "4.1.1. Coding style" section [1].
>
> Another thing, checking the new code and accepting code style violations (if any) on per-patch basis.
That would indeed be my preference, from what I've seen the
clang-format based style could live together with the previous style,
there doesn't seem to be any irreconcilable style differences that
would prevent new and old code chunks from being adjacent.
Thanks, Roger.
next prev parent reply other threads:[~2025-02-18 11:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 10:21 [PATCH 0/2] code style exercise: Drivers folder samples Oleksandr Andrushchenko
2025-02-16 10:21 ` [PATCH 1/2] code style: Format ns16550 driver Oleksandr Andrushchenko
2025-02-17 10:20 ` Jan Beulich
2025-02-19 12:39 ` Oleksandr Andrushchenko
2025-02-19 13:18 ` Jan Beulich
2025-02-19 13:52 ` Oleksandr Andrushchenko
2025-02-19 14:05 ` Jan Beulich
2025-02-19 15:40 ` Oleksandr Andrushchenko
2025-02-19 16:01 ` Jan Beulich
2025-02-23 7:53 ` Oleksandr Andrushchenko
2025-02-19 14:23 ` Oleksandr Andrushchenko
2025-02-19 14:58 ` Jan Beulich
2025-02-16 10:21 ` [PATCH 2/2] code style: Format ACPI tables Oleksandr Andrushchenko
2025-02-16 11:58 ` [PATCH 0/2] code style exercise: Drivers folder samples Andrew Cooper
2025-02-16 17:11 ` Oleksandr Andrushchenko
2025-02-19 12:49 ` Andrew Cooper
2025-02-19 12:51 ` Oleksandr Andrushchenko
2025-02-19 13:19 ` Oleksandr Andrushchenko
2025-02-19 13:42 ` Andrew Cooper
2025-02-17 9:07 ` Jan Beulich
2025-02-18 2:36 ` Stefano Stabellini
2025-02-18 11:34 ` Jan Beulich
2025-02-19 12:43 ` Oleksandr Andrushchenko
2025-02-19 12:49 ` Jan Beulich
2025-02-19 12:54 ` Oleksandr Andrushchenko
2025-02-20 1:34 ` Stefano Stabellini
2025-02-23 7:42 ` Oleksandr Andrushchenko
2025-02-24 10:55 ` Jan Beulich
2025-02-25 18:09 ` Oleksandr Andrushchenko
2025-02-18 9:56 ` Grygorii Strashko
2025-02-18 11:41 ` Roger Pau Monné [this message]
2025-02-19 12:50 ` Oleksandr Andrushchenko
2025-02-18 10:01 ` Luca Fancellu
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=Z7RxzdK9wJy5K_c4@macbook.local \
--to=roger.pau@citrix.com \
--cc=Artem_Mygaiev@epam.com \
--cc=Luca.Fancellu@arm.com \
--cc=andr2000@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=grygorii_strashko@epam.com \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.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.