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>,
	"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.13
Date: Sat, 14 Dec 2024 07:52:17 +0100	[thread overview]
Message-ID: <20241214065217.195385-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these two fixes for Rust.

They have both been in linux-next for three rounds this week.

No conflicts expected.

I picked a DRM fix, but they will eventually pick them on their side.

Thanks!

Cheers,
Miguel

The following changes since commit fac04efc5c793dccbd07e2d59af9f90b7fc0dca4:

  Linux 6.13-rc2 (2024-12-08 14:03:39 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 7a5f93ea5862da91488975acaa0c7abd508f192b:

  rust: kbuild: set `bindgen`'s Rust target version (2024-12-10 01:06:10 +0100)

----------------------------------------------------------------
Rust fixes for v6.13

Toolchain and infrastructure:

 - Set bindgen's Rust target version to prevent issues when pairing
   older rustc releases with newer bindgen releases, such as
   bindgen >= 0.71.0 and rustc < 1.82 due to unsafe_extern_blocks.

drm/panic:

 - Remove spurious empty line detected by a new Clippy warning.

----------------------------------------------------------------
Miguel Ojeda (2):
      drm/panic: remove spurious empty line to clean warning
      rust: kbuild: set `bindgen`'s Rust target version

 drivers/gpu/drm/drm_panic_qr.rs |  1 -
 rust/Makefile                   | 15 ++++++++++++++-
 2 files changed, 14 insertions(+), 2 deletions(-)

             reply	other threads:[~2024-12-14  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14  6:52 Miguel Ojeda [this message]
2024-12-14 16:54 ` [GIT PULL] Rust fixes for 6.13 Linus Torvalds
2024-12-14 16:59   ` Linus Torvalds
2024-12-14 17:09     ` Willy Tarreau
2024-12-14 18:16   ` Miguel Ojeda
2024-12-14 17:06 ` 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=20241214065217.195385-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