[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5bd688b0-7694-0a96-67e6-7137c018c9a5@schinagl.nl>
Date: Thu, 28 Jul 2022 22:45:08 +0200
From: Olliver Schinagl <oliver+list@...inagl.nl>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Gary Guo <gary@...yguo.net>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Miguel Ojeda <ojeda@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
rust-for-linux <rust-for-linux@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/13] [RFC] Rust support
Hey Greg,
On 28-07-2022 14:09, Greg Kroah-Hartman wrote:
> On Thu, Jul 28, 2022 at 11:21:14AM +0100, Gary Guo wrote:
>> Rust requires braces around branches of if expression, and C doesn't.
>> So in kernel coding style you often have:
>>
>> if (condition) do_something();
>
> That is not a valid kernel coding style, and our tools should catch this
> and prevent it from being added to the kernel tree.
Are you sure? I'm not sure if this isn't true today, but I've certainly
seen old code where this definitely was done. Was all of this cleaned up
in the last 2+ years?
Olliver
>
> thanks,
>
> greg k-h
Powered by blists - more mailing lists