[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59ebc5f2-7d58-49f5-83f1-c954705f3953@proton.me>
Date: Wed, 24 Jul 2024 19:13:08 +0000
From: Benno Lossin <benno.lossin@...ton.me>
To: Greg KH <greg@...ah.com>
Cc: Jonathan Corbet <corbet@....net>, Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, Wedson Almeida Filho <wedsonaf@...il.com>, Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>, Andreas Hindborg <a.hindborg@...sung.com>, Alice Ryhl <aliceryhl@...gle.com>, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [RFC PATCH 1/5] doc: rust: create safety standard
On 18.07.24 06:45, Greg KH wrote:
> On Wed, Jul 17, 2024 at 10:12:29PM +0000, Benno Lossin wrote:
>> +Because unsoundness issues have the potential for allowing safe code to experience UB, they are
>> +treated similarly to actual bugs with UB. Their fixes should also be included in the stable tree.
>
> Odd extra space before "stable".
>
> Also, link to the stable kernel rules here when you reference "stable
> tree"? That will explain what you mean here.
Sure will add it, do you mean Documentation/process/stable-kernel-rules.rst?
Or a different file?
---
Cheers,
Benno
Powered by blists - more mailing lists