[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=-bV_=TUoH6gLnPwTcxROBqyrCpOpbumki_S+po1TPhQ@mail.gmail.com>
Date: Fri, 27 Sep 2024 10:39:43 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <benno.lossin@...ton.me>
Cc: kernel test robot <lkp@...el.com>, Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...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@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>, llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
Greg KH <greg@...ah.com>, Simona Vetter <simona.vetter@...ll.ch>, linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v2 1/2] rust: add untrusted data abstraction
On Fri, Sep 27, 2024 at 12:15 AM Benno Lossin <benno.lossin@...ton.me> wrote:
>
> Personally, I would prefer adding a symbol. Since if we allow it, then
> it might take a long time until the code is removed once we increase the
> minimum version.
>
> It would be best, if it produces an error when we raise the minimum
> version beyond the one represented by the symbol. Is that already the
> case?
No -- that is a nice idea that I guess could be implemented in Kconfig
somewhere (i.e. when checking conditions). However, one of the common
things to do when upgrading the minimum is to review/clean the
`*_VERSION` uses anyway (and they may occur outside Kconfig files
too), and also sometimes one wants to upgrade a minimum without doing
the cleanups immediately (e.g. the recently proposed GCC 8.1 upgrade).
> Gave it a try and I also can't reproduce the error there...
Hmm... I think CE uses the Rust-provided binaries (and I guess the
playground too). Do you have a link ("Share" in CE)?
Cheers,
Miguel
Powered by blists - more mailing lists