Rust for Linux List
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"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
Subject: [GIT PULL] Rust fixes for 6.11
Date: Fri, 16 Aug 2024 19:16:22 +0200	[thread overview]
Message-ID: <20240816171622.41357-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these fixes for Rust.

They have been in linux-next for a week or more.

No conflicts expected. No changes to the C side.

Thanks!

Cheers,
Miguel

The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:

  Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)

are available in the Git repository at:

  https://github.com/Rust-for-Linux/linux.git tags/rust-fixes-6.11

for you to fetch changes up to 0eba65f0310d3c7d5516c7fd4c172d0bfa8b285b:

  rust: x86: remove `-3dnow{,a}` from target features (2024-08-10 00:05:10 +0200)

----------------------------------------------------------------
Rust fixes for v6.11

 - Fix '-Os' Rust 1.80.0+ builds adding more intrinsics (also tweaked
   in upstream Rust for the upcoming 1.82.0).

 - Fix support for the latest version of rust-analyzer due to a change
   on rust-analyzer config file semantics (considered a fix since most
   developers use the latest version of the tool, which is the only one
   actually supported by upstream). I am discussing stability of the
   config file with upstream -- they may be able to start versioning it.

 - Fix GCC 14 builds due to '-fmin-function-alignment' not skipped for
   libclang (bindgen).

 - A couple Kconfig fixes around '{RUSTC,BINDGEN}_VERSION_TEXT' to
   suppress error messages in a foreign architecture chroot and to use a
   proper default format.

 - Clean 'rust-analyzer' target warning due to missing recursive make
   invocation mark.

 - Clean Clippy warning due to missing indentation in docs.

 - Clean LLVM 19 build warning due to removed 3dnow feature upstream.

----------------------------------------------------------------
Masahiro Yamada (2):
      rust: suppress error messages from CONFIG_{RUSTC,BINDGEN}_VERSION_TEXT
      rust: fix the default format for CONFIG_{RUSTC,BINDGEN}_VERSION_TEXT

Miguel Ojeda (4):
      rust: macros: indent list item in `module!`'s docs
      rust: add intrinsics to fix `-Os` builds
      kbuild: rust-analyzer: mark `rust_is_available.sh` invocation as recursive
      rust: x86: remove `-3dnow{,a}` from target features

Sarthak Singh (1):
      rust: Support latest version of `rust-analyzer`

Zehui Xu (1):
      kbuild: rust: skip -fmin-function-alignment in bindgen flags

 Makefile                          | 2 +-
 init/Kconfig                      | 4 ++--
 rust/Makefile                     | 8 ++++----
 rust/compiler_builtins.rs         | 3 +++
 rust/macros/lib.rs                | 2 +-
 scripts/generate_rust_analyzer.py | 6 +++++-
 scripts/generate_rust_target.rs   | 4 ++--
 7 files changed, 18 insertions(+), 11 deletions(-)

             reply	other threads:[~2024-08-16 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 17:16 Miguel Ojeda [this message]
2024-08-16 18:28 ` [GIT PULL] Rust fixes for 6.11 pr-tracker-bot

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=20240816171622.41357-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-kernel@vger.kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wedsonaf@gmail.com \
    /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