All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, Artem_Mygaiev@epam.com,
	jbeulich@suse.com, Luca.Fancellu@arm.com, roger.pau@citrix.com,
	marmarek@invisiblethingslab.com, anthony.perard@vates.tech
Subject: Re: [PATCH 0/2] code style exercise: Drivers folder samples
Date: Wed, 19 Feb 2025 15:19:55 +0200	[thread overview]
Message-ID: <c16b3ae4-dc26-4e08-81ef-47b6ae4914fe@gmail.com> (raw)
In-Reply-To: <013ab6c2-65af-4dd7-8796-ac5178a7e600@gmail.com>



On 19.02.25 14:51, Oleksandr Andrushchenko wrote:
> Hello, Andrew!
>
> On 19.02.25 14:49, Andrew Cooper wrote:
>> On 16/02/2025 5:11 pm, Oleksandr Andrushchenko wrote:
>>> Hello, Roger!
>>>
>>> Please find the branch with all the conversions [1].
>>> Unfortunately I cannot provide a branch as seen with
>>> diff --ignore-all-space as such a patch will not simply apply.
>>>
>>> Stay safe,
>>> Oleksandr Andrushchenko
>>>
>>> On 16.02.25 13:58, Andrew Cooper wrote:
>>>> On 16/02/2025 10:21 am, Oleksandr Andrushchenko wrote:
>>>>> There are two diff files which show what happens in case the same is
>>>>> applied to the whole xen/drivers directory:
>>>>> - first one is the result of the "git diff" command, 1.2M [3]
>>>>> - the second one is for "git diff --ignire-all-space", 600K [4]
>>>> Please can you format everything, and put it on a branch somewhere, so
>>>> people can browse.
>>>>
>>>> ~Andrew
>>> [1] https://github.com/andr2000/xen/tree/clang_ml_drivers_v002_diff
force pushed to the same branch for all Xen
>> That appears to only be drivers/
> I thought that was the agreement, so we start from the drivers first
>>
>> Please do *everything*.  I want to see what this does to files I
>> consider to be pretty clean Xen-style.
> Sure
>>
>> ~Andrew
>>
> Thank you,
> Oleksandr



  reply	other threads:[~2025-02-19 13:20 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 [this message]
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é
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=c16b3ae4-dc26-4e08-81ef-47b6ae4914fe@gmail.com \
    --to=andr2000@gmail.com \
    --cc=Artem_Mygaiev@epam.com \
    --cc=Luca.Fancellu@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=roger.pau@citrix.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.