workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>,
	Wedson Almeida Filho <wedsonaf@gmail.com>,
	Alex Gaynor <alex.gaynor@gmail.com>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@samsung.com>,
	"Alice Ryhl" <aliceryhl@google.com>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kbuild@vger.kernel.org, workflows@vger.kernel.org
Subject: [PATCH v2 00/13] Support several Rust toolchain versions
Date: Tue,  9 Jul 2024 18:05:55 +0200	[thread overview]
Message-ID: <20240709160615.998336-1-ojeda@kernel.org> (raw)

Hi all,

A few things improved here and there, and rebased on top of `rust-next`.

The changelog is attached to each patch.

I kept the `Tested-by`s since most of the changes are on documentation
or comments, though I did remove them on the patch that changed the most
just in case (even for that one, I think Benno's and Andreas' setup
would not have made a difference).

I plan to put this series into `rust-next` very soon so that it goes
into the merge window.

Previous cover letter:

  v1: https://lore.kernel.org/rust-for-linux/20240701183625.665574-1-ojeda@kernel.org/

Thanks!

Cheers,
Miguel

Miguel Ojeda (13):
  rust: macros: indent list item in `paste!`'s docs
  rust: init: simplify from `map_err` to `inspect_err`
  rust: allow `dead_code` for never constructed bindings
  rust: relax most deny-level lints to warnings
  rust: simplify Clippy warning flags set
  rust: start supporting several compiler versions
  rust: avoid assuming a particular `bindgen` build
  rust: work around `bindgen` 0.69.0 issue
  rust: start supporting several `bindgen` versions
  rust: warn about `bindgen` versions 0.66.0 and 0.66.1
  kbuild: rust: add `rustc-version` support
  rust: support the new `-Zub-checks` flag
  docs: rust: quick-start: add section on Linux distributions

 Documentation/process/changes.rst        |   9 +-
 Documentation/rust/quick-start.rst       | 136 +++++++++++++++++------
 Makefile                                 |  31 +++---
 init/Kconfig                             |  11 +-
 lib/Kconfig.debug                        |  18 +++
 rust/Makefile                            |   4 +-
 rust/bindings/lib.rs                     |   1 +
 rust/kernel/init.rs                      |  13 +--
 rust/macros/lib.rs                       |   2 +-
 rust/uapi/lib.rs                         |   1 +
 scripts/Kconfig.include                  |   6 +
 scripts/Makefile.compiler                |   4 +
 scripts/rust_is_available.sh             |  33 +++---
 scripts/rust_is_available_bindgen_0_66.h |   2 +
 scripts/rust_is_available_test.py        |  59 ++++++----
 scripts/rustc-version.sh                 |  52 +++++++++
 16 files changed, 274 insertions(+), 108 deletions(-)
 create mode 100644 scripts/rust_is_available_bindgen_0_66.h
 create mode 100755 scripts/rustc-version.sh


base-commit: fc6e66f4696b63b8a2645a2bcea407cb04bd0666
--
2.45.2

             reply	other threads:[~2024-07-09 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 16:05 Miguel Ojeda [this message]
2024-07-09 16:06 ` [PATCH v2 06/13] rust: start supporting several compiler versions Miguel Ojeda
2024-07-09 16:06 ` [PATCH v2 13/13] docs: rust: quick-start: add section on Linux distributions Miguel Ojeda
2024-07-10  9:04 ` [PATCH v2 00/13] Support several Rust toolchain versions Miguel Ojeda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240709160615.998336-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=wedsonaf@gmail.com \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).