rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"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@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 6.12 (2nd)
Date: Sat, 19 Oct 2024 00:53:29 +0200	[thread overview]
Message-ID: <20241018225329.235175-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these fixes for Rust (second round).

They have all been in linux-next for a week.

No conflicts expected.

Thanks!

Cheers,
Miguel

The following changes since commit 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b:

  Linux 6.12-rc2 (2024-10-06 15:32:27 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 8b8ca9c25fe69c2162e3235c7d6c341127abeed6:

  cfi: fix conditions for HAVE_CFI_ICALL_NORMALIZE_INTEGERS (2024-10-13 22:23:13 +0200)

----------------------------------------------------------------
Rust fixes for v6.12 (2nd)

Toolchain and infrastructure:

 - Fix several issues with the 'rustc-option' macro. It includes a
   refactor from Masahiro of three '{cc,rust}-*' macros, which is not
   a fix but avoids repeating the same commands (which would be several
   lines in the case of 'rustc-option').

 - Fix conditions for 'CONFIG_HAVE_CFI_ICALL_NORMALIZE_INTEGERS'. It
   includes the addition of 'CONFIG_RUSTC_LLVM_VERSION', which is not a
   fix but is needed for the actual fix.

And a trivial grammar fix.

----------------------------------------------------------------
Alice Ryhl (2):
      kbuild: fix issues with rustc-option
      cfi: fix conditions for HAVE_CFI_ICALL_NORMALIZE_INTEGERS

Gary Guo (1):
      kbuild: rust: add `CONFIG_RUSTC_LLVM_VERSION`

Masahiro Yamada (1):
      kbuild: refactor cc-option-yn, cc-disable-warning, rust-option-yn macros

Timo Grautstueck (1):
      lib/Kconfig.debug: fix grammar in RUST_BUILD_ASSERT_ALLOW

 arch/Kconfig                  | 26 ++++++++++++--------------
 init/Kconfig                  |  8 ++++++--
 lib/Kconfig.debug             |  2 +-
 scripts/Kconfig.include       |  3 +++
 scripts/Makefile.compiler     | 14 +++++++-------
 scripts/rustc-llvm-version.sh | 22 ++++++++++++++++++++++
 6 files changed, 51 insertions(+), 24 deletions(-)
 create mode 100755 scripts/rustc-llvm-version.sh

             reply	other threads:[~2024-10-18 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 22:53 Miguel Ojeda [this message]
2024-10-19 16:01 ` [GIT PULL] Rust fixes for 6.12 (2nd) 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=20241018225329.235175-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=a.hindborg@kernel.org \
    --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=tmgross@umich.edu \
    --cc=torvalds@linux-foundation.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).