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: <26fad7ef-0564-4250-ab8b-e8263c3d7dbf@lunn.ch> Date: Sat, 28 Oct 2023 20:18:41 +0200 From: Andrew Lunn <andrew@...n.ch> To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com> Cc: Benno Lossin <benno.lossin@...ton.me>, Boqun Feng <boqun.feng@...il.com>, FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, tmgross@...ch.edu, wedsonaf@...il.com Subject: Re: [PATCH net-next v7 1/5] rust: core abstractions for network PHY drivers > But yes, it makes a difference in the output it generates (if we are > talking about the pointed-to), e.g. > > void f(struct S *); // *mut S > void f(const struct S *); // *const S > > Being const-correct would be a good change for C in any case. I have a patchset which changes a few functions to use const struct *phydev. I will post them next cycle. They are a bit invasive, so i don't want to do it now, this close to the merge window. Andrew
Powered by blists - more mailing lists