pin-init sync v6.18
Subsystems (2)
Benno Lossin
maintainercover pin-init sync v6.18
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
Signature · 1 line
2.50.1
Benno Lossin
maintainerPATCH 1/2 rust: pin-init: examples: error: use `Error` in `fn main()`
When running this example with no cargo features enabled, the compiler warns on 1.89:
error: struct Error is never constructed
--> examples/error.rs:11:12
|
11 | pub struct Error;
| ^^^^^
| = note: -D dead-code implied by -D warnings
= help: to override -D warnings add #[allow(dead_code)]
Thus use the error in the main function to avoid this warning.
--- rust/pin-init/examples/error.rs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
rust/pin-init/examples/error.rs +3 -1
@@ -24,4 +24,6 @@ fn from(_: AllocError) -> Self { }#[allow(dead_code)] -fn main () {} +fn main () { +let _ =Error ; +}
base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
Signature · 1 line
2.50.1
Benno Lossin
maintainerPATCH 2/2 rust: pin-init: README: add information banner on the rename to `pin-init`
In reply to Benno Lossin--- rust/pin-init/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+)
rust/pin-init/README.md +12 -0
@@ -6,6 +6,18 @@  # `pin-init` +> [!NOTE] +> +> This crate was originally named [`pinned-init`], but the migration to +> `pin-init` is not yet complete. The `legcay` branch contains the current +> version of the `pinned-init` crate & the `main` branch already incorporates +> the rename to `pin-init`. +> +> There are still some changes needed on the kernel side before the migration +> can be completed. + +[`pinned-init`]: https://crates.io/crates/pinned-init + <!-- cargo-rdme start --> Library to safely and fallibly initialize pinned `struct`s using in-place constructors.
Signature · 1 line
2.50.1
Alice Ryhl
reviewerRe: [PATCH 2/2] rust: pin-init: README: add information banner on the rename to `pin-init`
Quoted 12 lines · Benno Lossin
Link https://github.com/Rust-for-Linux/pin-init/pull/81/commits/3cf4658e2db96b4a6b26db9478250de2ffcfa1feSigned-off-by Benno Lossin <[email protected]>--- rust/pin-init/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+)rust/pin-init/README.md +0
-0
rust/pin-init/README.md line 12
Quoted 7 lines
rust/pin-init/README.md +4
-0@@ -6,6 +6,18 @@  # `pin-init` +> [!NOTE] +> +> This crate was originally named [`pinned-init`], but the migration to +> `pin-init` is not yet complete. The `legcay` branch contains the current
typo
Quoted 15 lines · Benno Lossin
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/82Note 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: useErrorinfn main()
rust: pin-init: README: add information banner on the rename to
Quoted 8 lines
`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
Applied to pin-init-next, thanks everyone!
I left the typo in, since I will need to fix that upstream next cycle. The banner might also be gone next cycle, so I don't think it matters too much.
---
Cheers,
Benno