[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023100916-crushing-sprawl-30a4@gregkh>
Date: Mon, 9 Oct 2023 15:06:30 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>,
FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, tmgross@...ch.edu,
Andrea Righi <andrea.righi@...onical.com>
Subject: Re: [PATCH net-next v3 0/3] Rust abstractions for network PHY drivers
On Mon, Oct 09, 2023 at 02:53:00PM +0200, Miguel Ojeda wrote:
> On Mon, Oct 9, 2023 at 2:48 PM Andrew Lunn <andrew@...n.ch> wrote:
> >
> > Any ideas?
>
> That is `RETHUNK` and `X86_KERNEL_IBT`.
>
> Since this will keep confusing people, I will make it a `depends on !`
> as discussed in the past. I hope it is OK for e.g. Andrea.
That's not ok as you want that option enabled on systems that have those
broken processors which need this option for proper security. You would
be forcing people to disable this to enable Rust support?
confused,
greg k-h
Powered by blists - more mailing lists