From: Benno Lossin <benno.lossin@proton.me>
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" <benno.lossin@proton.me>,
"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 fixes
Date: Mon, 07 Apr 2025 20:18:11 +0000 [thread overview]
Message-ID: <20250407201755.649153-1-benno.lossin@proton.me> (raw)
Sync from the upstream repository [1]. This is the first time I used my
sync script to port the patches, so if you see any issues, please let me
know. You can find the commits in my repo [2].
Just two small patches fixing one issue that got overlooked, since it
was fixed at the same time the series got merged. And the other fixes a
markdown papercut that I found during review of the previous fix.
[1]: https://github.com/Rust-for-Linux/pin-init
[2]: https://github.com/y86-dev/linux/tree/pin-init-sync
Github PRs included in this sync:
* alloc: restrict `impl ZeroableOption` for `Box` to `T: Sized`
https://github.com/Rust-for-Linux/pin-init/pull/32
---
Miguel Ojeda (2):
rust: pin-init: alloc: restrict `impl ZeroableOption` for `Box` to `T:
Sized`
rust: pin-init: use Markdown autolinks in Rust comments
rust/pin-init/examples/pthread_mutex.rs | 2 +-
rust/pin-init/src/alloc.rs | 8 +++-----
rust/pin-init/src/lib.rs | 2 +-
3 files changed, 5 insertions(+), 7 deletions(-)
base-commit: a2cc6ff5ec8f91bc463fd3b0c26b61166a07eb11
--
2.48.1
next reply other threads:[~2025-04-07 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 20:18 Benno Lossin [this message]
2025-04-07 20:18 ` [PATCH 1/2] rust: pin-init: alloc: restrict `impl ZeroableOption` for `Box` to `T: Sized` Benno Lossin
2025-04-07 20:18 ` [PATCH 2/2] rust: pin-init: use Markdown autolinks in Rust comments Benno Lossin
2025-04-08 19:48 ` [PATCH 0/2] pin-init fixes Miguel Ojeda
2025-04-08 19:59 ` Miguel Ojeda
2025-04-08 21:49 ` Benno Lossin
2025-04-09 14:15 ` Miguel Ojeda
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=20250407201755.649153-1-benno.lossin@proton.me \
--to=benno.lossin@proton.me \
--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).