All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miguel Ojeda <ojeda@kernel.org>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 6.15 merge
Date: Mon, 31 Mar 2025 14:29:26 +0200	[thread overview]
Message-ID: <20250331122926.607374-1-ojeda@kernel.org> (raw)

Hi Linus,

A small fix due to a typo during merge.

Since Andrei had already sent a fix for it, I am sending this as a PR in
case you prefer that, but of course please feel free to directly apply
it as a patch instead.

Thanks!

Cheers,
Miguel

The following changes since commit 4e82c87058f45e79eeaa4d5bcc3b38dd3dce7209:

  Merge tag 'rust-6.15' of git://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux (2025-03-30 17:03:26 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git tags/rust-fixes-6.15-merge

for you to fetch changes up to c1f4534b213d7be41b5d8b815a42d201a8f2978f:

  scripts: generate_rust_analyzer: fix pin-init name in kernel deps (2025-03-31 10:50:54 +0200)

----------------------------------------------------------------
Rust fixes for v6.15 merge

Fix 'generate_rust_analyzer.py' due to typo during merge.

----------------------------------------------------------------
Andrei Lalaev (1):
      scripts: generate_rust_analyzer: fix pin-init name in kernel deps

 scripts/generate_rust_analyzer.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2025-03-31 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 12:29 Miguel Ojeda [this message]
2025-03-31 18:33 ` [GIT PULL] Rust fixes for 6.15 merge Linus Torvalds
2025-04-01 11:02   ` Miguel Ojeda
2025-04-01  2:03 ` 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=20250331122926.607374-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.