From: Benno Lossin <benno.lossin@proton.me>
To: Tamir Duberstein <tamird@gmail.com>
Cc: "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>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] rust: pin_init_internal: fix rust-analyzer `mod quote`
Date: Thu, 20 Mar 2025 14:10:47 +0000 [thread overview]
Message-ID: <D8L5JXRXHX0N.UIFZ5M15FB3S@proton.me> (raw)
In-Reply-To: <CAJ-ks9nTmno12ZC4DnLxV_b0NLUK5Kn5K+cRi4BEvKtveQzJjg@mail.gmail.com>
On Thu Mar 20, 2025 at 2:31 PM CET, Tamir Duberstein wrote:
> On Thu, Mar 20, 2025 at 8:16 AM Benno Lossin <benno.lossin@proton.me> wrote:
>> I'd rather not have this change, since this will introduce a dangling
>> symlink upstream [1].
>>
>> [1]: https://github.com/rust-for-Linux/pin-init
>
> I agree it's aesthetically displeasing. I'm not aware of any
> alternative that fixes the development workflow of this crate in the
> kernel.
I don't think it's too bad, and this code is going away soon-ish
anyways.
---
Cheers,
Benno
next prev parent reply other threads:[~2025-03-20 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 1:35 Tamir Duberstein
2025-03-20 7:46 ` Alice Ryhl
2025-03-20 10:16 ` Tamir Duberstein
2025-03-20 12:16 ` Benno Lossin
2025-03-20 13:31 ` Tamir Duberstein
2025-03-20 14:10 ` Benno Lossin [this message]
2025-03-20 14:15 ` Tamir Duberstein
2025-12-22 12:43 ` Tamir Duberstein
2025-12-23 1:32 ` 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=D8L5JXRXHX0N.UIFZ5M15FB3S@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=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--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
all inboxes | Powered by JetHome®