From: "Benno Lossin" <lossin@kernel.org>
To: "Guilherme Giacomo Simoes" <trintaeoitogc@gmail.com>,
<miguel.ojeda.sandonis@gmail.com>
Cc: <a.hindborg@kernel.org>, <airlied@gmail.com>,
<alex.gaynor@gmail.com>, <aliceryhl@google.com>,
<anisse@astier.eu>, <bjorn3_gh@protonmail.com>,
<boqun.feng@gmail.com>, <dakr@kernel.org>,
<david.m.ertman@intel.com>, <dri-devel@lists.freedesktop.org>,
<fujita.tomonori@gmail.com>, <gary@garyguo.net>,
<gregkh@linuxfoundation.org>, <igor.korotin.linux@gmail.com>,
<ira.weiny@intel.com>, <leitao@debian.org>, <leon@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<maarten.lankhorst@linux.intel.com>, <mcgrof@kernel.org>,
<mripard@kernel.org>, <nouveau@lists.freedesktop.org>,
<ojeda@kernel.org>, <rafael@kernel.org>, <russ.weight@linux.dev>,
<rust-for-linux@vger.kernel.org>, <simona@ffwll.ch>,
<tamird@gmail.com>, <tmgross@umich.edu>, <tzimmermann@suse.de>,
<viresh.kumar@linaro.org>, <walmeida@microsoft.com>
Subject: Re: [PATCH] rust: module: remove deprecated author key
Date: Tue, 10 Jun 2025 14:55:55 +0200 [thread overview]
Message-ID: <DAIVBBJADWNR.1LLZJ6YWV8IN2@kernel.org> (raw)
In-Reply-To: <20250610123731.194853-1-trintaeoitogc@gmail.com>
On Tue Jun 10, 2025 at 2:37 PM CEST, Guilherme Giacomo Simoes wrote:
> Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrotes:
>> On Tue, Jun 10, 2025 at 12:12 PM Benno Lossin <lossin@kernel.org> wrote:
>> >
>> > Hmm, I guess a checkpatch lint fits better then?
>>
>> Yeah, that would work.
>>
>> Probably for the C side too -- from a quick grep I don't see it.
> Maybe, after this patch we can make a checkpatch change for check the `authors`
> key (and MODULE_AUTHOR for C side), and throw a WARN if the author is a name
> (not a url, or "rust for linux") and don't have a email address.
Most other authors fields that don't list explicit names use "Rust for
Linux Contributors", so we should probably scan for that instead.
But I think that we should no longer add any author fields using that.
Things with that are from way back in the day (when RfL was still out of
tree) where many people contributed to a single file, hence the use of
that phrase.
> Unless you guys tell me otherwise, I guess this is not so priority.
Yeah this isn't high priority. We can just make this into a
good-first-issue, then someone can eventually pick it up.
---
Cheers,
Benno
next prev parent reply other threads:[~2025-06-10 12:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4pEkPxIXoND4Ndog7RjFo36DrUhFW-OT8Z6Y21aYvhfqE0rgUEmYEGn2PStTYOsOfpXv0R8aWmboCdc0m8uZfA==@protonmail.internalid>
2025-06-09 12:22 ` [PATCH] rust: module: remove deprecated author key Guilherme Giacomo Simoes
2025-06-09 17:39 ` Miguel Ojeda
2025-06-09 17:47 ` Danilo Krummrich
2025-06-10 10:02 ` Greg KH
2025-06-10 0:57 ` Viresh Kumar
2025-06-10 8:24 ` Andreas Hindborg
2025-06-10 8:56 ` Benno Lossin
2025-06-10 8:57 ` Benno Lossin
2025-06-10 10:03 ` Miguel Ojeda
2025-06-10 10:09 ` Miguel Ojeda
2025-06-10 10:12 ` Benno Lossin
2025-06-10 10:16 ` Miguel Ojeda
2025-06-10 12:37 ` Guilherme Giacomo Simoes
2025-06-10 12:46 ` Miguel Ojeda
2025-06-10 12:55 ` Benno Lossin [this message]
2025-06-23 23:13 ` 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=DAIVBBJADWNR.1LLZJ6YWV8IN2@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anisse@astier.eu \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=david.m.ertman@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=igor.korotin.linux@gmail.com \
--cc=ira.weiny@intel.com \
--cc=leitao@debian.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcgrof@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
--cc=trintaeoitogc@gmail.com \
--cc=tzimmermann@suse.de \
--cc=viresh.kumar@linaro.org \
--cc=walmeida@microsoft.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 NNTP newsgroup(s).