lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <ada8d010-52ac-46c1-b839-8d3b3ed59ae1@lunn.ch> Date: Sat, 28 Oct 2023 17:00:55 +0200 From: Andrew Lunn <andrew@...n.ch> To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com> Cc: Jakub Kicinski <kuba@...nel.org>, FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, tmgross@...ch.edu, benno.lossin@...ton.me, wedsonaf@...il.com Subject: Re: [PATCH net-next v7 0/5] Rust abstractions for network PHY drivers On Sat, Oct 28, 2023 at 01:07:43PM +0200, Miguel Ojeda wrote: > On Sat, Oct 28, 2023 at 12:55 AM Andrew Lunn <andrew@...n.ch> wrote: > > > > You will probably find different levels of acceptance of 80 to 100 in > > different subsystems. So i'm not sure you will be able to achieve > > consistence. > > I would definitely agree if this were C. I happen to maintain > `.clang-format`, and it was an interesting process to approximate a > "common enough" style as the base one. > > But for Rust, it is easy, because all the code is new. All Rust files > are formatted the same way, across the entire kernel. I would say this is not a technical issue, but a social one. In order to keep the netdev people happy, you are going to limit it to 80. But i would not be too surprised if another subsystem says the code would be more readable with 100, like the C code in our subsystem. We want Rust to be 100 as well. Linux can be very fragmented like this across subsystems. Its just the way it is, and you might just have to fit in. I don't know, we will see. Andrew
Powered by blists - more mailing lists