From: Benno Lossin <lossin@kernel.org>
To: "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" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: rust-for-linux@vger.kernel.org
Subject: [PATCH 0/2] pin-init sync v6.18
Date: Fri, 5 Sep 2025 15:33:57 +0200 [thread overview]
Message-ID: <20250905133401.3312707-1-lossin@kernel.org> (raw)
Some very small changes coming from CI fixes & a readme update. These
changes are already merged upstream & originate from these pull
requests:
* https://github.com/Rust-for-Linux/pin-init/pull/79
* https://github.com/Rust-for-Linux/pin-init/pull/80
* https://github.com/Rust-for-Linux/pin-init/pull/81
* https://github.com/Rust-for-Linux/pin-init/pull/82
Note that 80 & 82 only changed CI, test & cargo files that aren't
included in the kernel tree.
Benno Lossin (2):
rust: pin-init: examples: error: use `Error` in `fn main()`
rust: pin-init: README: add information banner on the rename to
`pin-init`
rust/pin-init/README.md | 12 ++++++++++++
rust/pin-init/examples/error.rs | 4 +++-
2 files changed, 15 insertions(+), 1 deletion(-)
base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
--
2.50.1
next reply other threads:[~2025-09-05 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 13:33 Benno Lossin [this message]
2025-09-05 13:33 ` [PATCH 1/2] rust: pin-init: examples: error: use `Error` in `fn main()` Benno Lossin
2025-09-05 13:33 ` [PATCH 2/2] rust: pin-init: README: add information banner on the rename to `pin-init` Benno Lossin
2025-09-05 13:40 ` Alice Ryhl
2025-09-11 21:34 ` [PATCH 0/2] pin-init sync v6.18 Benno Lossin
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=20250905133401.3312707-1-lossin@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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).