Hello, Jan!
On 24.02.25 12:55, Jan Beulich wrote:
On 23.02.2025 08:42, Oleksandr Andrushchenko wrote:
On 20.02.25 03:34, Stefano Stabellini wrote:
On Wed, 19 Feb 2025, Oleksandr Andrushchenko wrote:
Yes, I do agree. But only if we talk about having an automated
code style check now (which is
On 23.02.2025 08:42, Oleksandr Andrushchenko wrote:
> On 20.02.25 03:34, Stefano Stabellini wrote:
>> On Wed, 19 Feb 2025, Oleksandr Andrushchenko wrote:
>>> Yes, I do agree. But only if we talk about having an automated
>>> code style check now (which is definitely the goal at some time).
>>> Befo
Hello, Stefano!
On 20.02.25 03:34, Stefano Stabellini wrote:
On Wed, 19 Feb 2025, Oleksandr Andrushchenko wrote:
Yes, I do agree. But only if we talk about having an automated
code style check now (which is definitely the goal at some time).
Before that we could still use the tool to take all t
On Wed, 19 Feb 2025, Oleksandr Andrushchenko wrote:
> Yes, I do agree. But only if we talk about having an automated
> code style check now (which is definitely the goal at some time).
> Before that we could still use the tool to take all that good that
> it does and manually prepare a set of patch
On 19/02/2025 1:19 pm, Oleksandr Andrushchenko wrote:
>
>
> 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 co
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 --igno
Hello, Jan!
On 19.02.25 14:49, Jan Beulich wrote:
On 19.02.2025 13:43, Oleksandr Andrushchenko wrote:
Hello, Jan, Stefano!
On 18.02.25 13:34, Jan Beulich wrote:
On 18.02.2025 03:36, Stefano Stabellini wrote:
On Mon, 17 Feb 2025, Jan Beulich wrote:
On 16.02.2025 11:21, Oleksandr Andrushchenk
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.
S
Hello, Grygorii!
On 18.02.25 11:56, Grygorii Strashko wrote:
On 16.02.25 12:21, Oleksandr Andrushchenko wrote:
Hello, everybody!
As agreed before [1] I am sending a series to show two samples of the
formatting done with clang-format. The clang-format configuration can be
found at [2]. It alr
On 19.02.2025 13:43, Oleksandr Andrushchenko wrote:
> Hello, Jan, Stefano!
>
> On 18.02.25 13:34, Jan Beulich wrote:
>> On 18.02.2025 03:36, Stefano Stabellini wrote:
>>> On Mon, 17 Feb 2025, Jan Beulich wrote:
On 16.02.2025 11:21, Oleksandr Andrushchenko wrote:
> 1. Const string arrays r
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.0
Hello, Jan, Stefano!
On 18.02.25 13:34, Jan Beulich wrote:
On 18.02.2025 03:36, Stefano Stabellini wrote:
On Mon, 17 Feb 2025, Jan Beulich wrote:
On 16.02.2025 11:21, Oleksandr Andrushchenko wrote:
1. Const string arrays reformatting
In case the length of items change we might need to introdu
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
On 18.02.2025 03:36, Stefano Stabellini wrote:
> On Mon, 17 Feb 2025, Jan Beulich wrote:
>> On 16.02.2025 11:21, Oleksandr Andrushchenko wrote:
>>> 1. Const string arrays reformatting
>>> In case the length of items change we might need to introduce a bigger
>>> change wrt new formatting of unaffec
Hi Oleksandr,
>
> 2. Long strings in ptintk violations
> I filed an issue on printk format strings [5]
> ==
> @@ -225,9 +231,9 @@ void __init acpi_table_print_madt_entry(struct
> acpi_subtable_header *header)
> p
On 16.02.25 12:21, Oleksandr Andrushchenko wrote:
Hello, everybody!
As agreed before [1] I am sending a series to show two samples of the
formatting done with clang-format. The clang-format configuration can be
found at [2]. It already has some notes on previous discussions when
Luca presente
On Mon, 17 Feb 2025, Jan Beulich wrote:
> On 16.02.2025 11:21, Oleksandr Andrushchenko wrote:
> > 1. Const string arrays reformatting
> > In case the length of items change we might need to introduce a bigger
> > change wrt new formatting of unaffected lines
> >
On 16.02.2025 11:21, Oleksandr Andrushchenko wrote:
> 1. Const string arrays reformatting
> In case the length of items change we might need to introduce a bigger
> change wrt new formatting of unaffected lines
> ==
>
> --
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 An
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 [
20 matches
Mail list logo
