From: "Gary Guo" <gary@garyguo.net>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
<lyude@redhat.com>, "Gary Guo" <gary@garyguo.net>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<rust-for-linux@vger.kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Simona Vetter" <simona@ffwll.ch>,
"Alice Ryhl" <aliceryhl@google.com>,
"Shankari Anand" <shankari.ak0208@gmail.com>,
"David Airlie" <airlied@gmail.com>,
"Asahi Lina" <lina+kernel@asahilina.net>,
"Atharv Dubey" <atharvd440@gmail.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>
Subject: Re: [PATCH] rust/drm: Fixup import styles
Date: Thu, 22 Jan 2026 23:01:46 +0000 [thread overview]
Message-ID: <DFVHQBHQR2CW.2X27B7EP1WXTO@garyguo.net> (raw)
In-Reply-To: <CANiq72k1b3DLEy_32ruWu1XBFK80oRDVzSer69ANL_232mmv-w@mail.gmail.com>
On Thu Jan 22, 2026 at 9:52 PM GMT, Miguel Ojeda wrote:
> On Thu, Jan 22, 2026 at 10:34 PM <lyude@redhat.com> wrote:
>>
>> Just a random musing - it would actually be quite nice if we could have
>> some sort of automated style check for this. I have to assume the linux
>> kernel probably isn't the only project out there with its own prelude…
>
> Yeah, that would be quite nice indeed -- we have discussed this a few
> times (most recently a couple weeks ago, including whether Klint could
> be used for that and for detecting "long import paths", i.e. when we
> have a re-export we prefer, but that has edge cases; as well as
> related bits like a `klint::moved` annotation -- Cc'ing Gary).
This is tracked in https://github.com/Rust-for-Linux/klint/issues/5.
Best,
Gary
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2026-01-22 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 20:28 Lyude Paul
2026-01-22 20:30 ` Danilo Krummrich
2026-01-22 21:34 ` lyude
2026-01-22 21:52 ` Miguel Ojeda
2026-01-22 23:01 ` Gary Guo [this message]
2026-01-23 9:37 ` 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=DFVHQBHQR2CW.2X27B7EP1WXTO@garyguo.net \
--to=gary@garyguo.net \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=atharvd440@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lina+kernel@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=shankari.ak0208@gmail.com \
--cc=simona@ffwll.ch \
/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®