[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025022230-urgency-imminent-6032@gregkh>
Date: Sat, 22 Feb 2025 12:07:14 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Martin Uecker <uecker@...raz.at>
Cc: Dan Carpenter <dan.carpenter@...aro.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Boqun Feng <boqun.feng@...il.com>, "H. Peter Anvin" <hpa@...or.com>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Christoph Hellwig <hch@...radead.org>,
rust-for-linux <rust-for-linux@...r.kernel.org>,
David Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
ksummit@...ts.linux.dev
Subject: Re: Rust kernel policy
On Sat, Feb 22, 2025 at 11:25:26AM +0100, Martin Uecker wrote:
> Thanks, this is useful. I was asking because it would be relatively
> easy to tweak the warnings in GCC too. GCC has similar heuristics for
> other warnings to turn them off in macros and one can certainly also
> make it smarter. (Again, the two problems here seem lack of communication
> and lack of resources. One needs to understand what needs to be done
> and someone has to do it. But even a limited amount of time/money could
> make a difference.)
For the time/money issue, there are a number of different groups
offering funding up for open source work like this. If you are in the
EU there are a bunch of different ones, and also openSSF from the Linux
Foundations funds work like this. So those might all be worth looking
into writing up a proposal if you want to do this.
hope this helps,
greg k-h
Powered by blists - more mailing lists