From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@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@samsung.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Arc methods for linked list
Date: Mon, 6 May 2024 00:27:17 +0200 [thread overview]
Message-ID: <CANiq72m6bgxtjax2not-8YVe88WFO6tLhqeK5wmYAzgVmKmh0A@mail.gmail.com> (raw)
In-Reply-To: <20240402-arc-for-list-v4-0-54db6440a9a9@google.com>
On Tue, Apr 2, 2024 at 3:07 PM Alice Ryhl <aliceryhl@google.com> wrote:
>
> This patchset contains two useful methods for the Arc type. They will be
> used in my Rust linked list implementation [1], which Rust Binder uses. See
> the Rust Binder RFC [2] for more information.
>
> Link: https://lore.kernel.org/rust-for-linux/20240402-linked-list-v1-0-b1c59ba7ae3b@google.com/ [1]
> Link: https://lore.kernel.org/rust-for-linux/20231101-rust-binder-v1-0-08ba9197f637@google.com/ [2]
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
[ Replace `try_new` with `new` in example since we now have the new
allocation APIs. - Miguel ]
Applied to `rust-next` -- thanks everyone!
Cheers,
Miguel
prev parent reply other threads:[~2024-05-05 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 13:07 [PATCH v4 0/2] Arc methods for linked list Alice Ryhl
2024-04-02 13:07 ` [PATCH v4 1/2] rust: sync: add `ArcBorrow::from_raw` Alice Ryhl
2024-04-02 13:07 ` [PATCH v4 2/2] rust: sync: add `Arc::into_unique_or_drop` Alice Ryhl
2024-05-05 22:27 ` Miguel Ojeda [this message]
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=CANiq72m6bgxtjax2not-8YVe88WFO6tLhqeK5wmYAzgVmKmh0A@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@samsung.com \
--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=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).