Hi Lars, Lars Kurth writes:
>> On 31 Jul 2019, at 17:54, Viktor Mitin <viktor.mitin...@gmail.com> wrote: >> >> Hi All, >> >> On Wed, Jul 31, 2019 at 7:45 PM Andrew Cooper <andrew.coop...@citrix.com> >> wrote: >>> >>> On 31/07/2019 17:24, Volodymyr Babchuk wrote: [...] > Ultimately we have to make some trade-offs as to what is more important: > a) automatic style checking - which means "common sense" can't be formalised > and there will be boundary cases like the above > b) reclaiming code review bandwidth through automation or going for a labour > intensive manual approach I like the linux kernel approach. checkpatch.pl produces errors, which are "no go", but it also produces warnings for such boundary cases, for maintainer/reviewer to decide. > I suggest we discuss in tomorrow's community call how to approach > this. Good idea, I'll attend. > I think the most important first step is to have a good view on the kind of > boundary cases that we may face Then we need some volunteer who'll try to cover all corner cases. -- Volodymyr Babchuk at EPAM _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel