From: "Danilo Krummrich" <dakr@kernel.org>
To: "Alice Ryhl" <aliceryhl@google.com>
Cc: <daniel.almeida@collabora.com>, <ojeda@kernel.org>,
<boqun@kernel.org>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
<a.hindborg@kernel.org>, <tmgross@umich.edu>, <tamird@kernel.org>,
<acourbot@nvidia.com>, <work@onurozkan.dev>,
<bhelgaas@google.com>, <kwilczynski@kernel.org>,
<gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<mhi@mailbox.org>, <driver-core@lists.linux.dev>,
<rust-for-linux@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rust: irq: make Registration compatible with lifetime-bound drivers
Date: Tue, 07 Jul 2026 16:12:07 +0200 [thread overview]
Message-ID: <DJSEF840P5ZP.10CNUQ0UHDLW8@kernel.org> (raw)
In-Reply-To: <ak0FAGpJtUH7VvHQ@google.com>
On Tue Jul 7, 2026 at 3:54 PM CEST, Alice Ryhl wrote:
> Why are the implementations for Arc/Box being removed?
The lifetime design enables us to just store references for shared ownership,
rather the needing a reference count, so it seems reasonable to remove those
blanket impls.
We could keep them a little longer until pin-init has self-referencial support,
but on the other hand they don't enable anything and are just for covinience, so
I'd rather drop them.
prev parent reply other threads:[~2026-07-07 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 21:09 [PATCH] rust: irq: make Registration compatible with lifetime-bound drivers Danilo Krummrich
2026-07-03 21:19 ` sashiko-bot
2026-07-07 13:40 ` Daniel Almeida
2026-07-07 13:54 ` Alice Ryhl
2026-07-07 14:12 ` Danilo Krummrich [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=DJSEF840P5ZP.10CNUQ0UHDLW8@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=driver-core@lists.linux.dev \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mhi@mailbox.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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.