[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a23f2da-8f98-4ca2-8ca7-bb264ea676dd@lunn.ch>
Date: Mon, 9 Oct 2023 15:24:58 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: FUJITA Tomonori <fujita.tomonori@...il.com>, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, greg@...ah.com, 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.
I really do suggest you work on your kconfig. The expectation is any
configuration that kconfig is happy with will build. People like Arnd
Bergmann do lots of randconfig builds. We don't want his work upset by
Rust code.
And as a Rust beginning, i find this pretty unfriendly, in that i
followed https://docs.kernel.org/rust/quick-start.html but did not get
a working build.
Andrew
Powered by blists - more mailing lists