From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements.
Date: Mon, 21 Oct 2024 09:49:56 +0200 (CEST) [thread overview]
Message-ID: <a520d1f5-8273-d67e-97fe-67f73edce9f1@linux-m68k.org> (raw)
In-Reply-To: <2024101835-tiptop-blip-09ed@gregkh>
Hi Greg,
Thanks for your patch, which is now commit 6e90b675cf942e50
("MAINTAINERS: Remove some entries due to various compliance
requirements.") in v6.12-rc4.
On Fri, 18 Oct 2024, Greg Kroah-Hartman wrote:
> Remove some entries due to various compliance requirements. They can come
> back in the future if sufficient documentation is provided.
This is very vague...
What are "various compliance requirements"?
What does "sufficient documentation" mean?
I can guess, but I think it's better to spell out the rules, as Linux
kernel development is done "in the open". I am also afraid this is
opening the door for further (ab)use...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-10-21 7:50 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 11:31 [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements Greg Kroah-Hartman
2024-10-21 7:49 ` Geert Uytterhoeven [this message]
2024-10-21 16:29 ` Wolfram Sang
2024-10-24 6:56 ` Lukas Wunner
2024-10-24 15:39 ` James Bottomley
2024-10-24 18:41 ` NotYourFox
2024-10-26 12:00 ` Angry Dev
2024-10-26 16:27 ` John Mcenroy
2024-10-30 13:34 ` metux
2024-10-21 12:02 ` Geert Uytterhoeven
2024-10-23 6:30 ` WangYuli
2024-10-23 7:32 ` Mingcong Bai
2024-10-23 8:09 ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Kexy Biscuit
2024-10-23 8:26 ` Nikita Travkin
2024-10-23 8:35 ` WangYuli
2024-10-23 9:04 ` Mingcong Bai
2024-10-23 9:28 ` Tonghao Zhang
2024-10-23 10:27 ` Nikita Shubin
2024-10-23 14:47 ` Lance Yang
2024-10-23 15:04 ` Sergio Paracuellos
2024-10-23 16:22 ` Yao Zi
2024-10-23 16:51 ` Tor Vic
2024-10-23 17:45 ` Linus Torvalds
2024-10-23 18:56 ` Phillip Susi
2024-10-23 19:15 ` Peter Cai
2024-10-23 19:19 ` Linus Torvalds
2024-10-23 19:28 ` Peter Cai
2024-10-24 21:01 ` Mikhail Novosyolov
2024-10-25 7:11 ` Nikolay Kichukov
2024-10-23 19:50 ` Tor Vic
2024-10-23 22:14 ` NotYourFox
2024-10-24 7:11 ` Integral
[not found] ` <20241024095708.189649-1-isage.dna@gmail.com>
2024-10-24 15:41 ` Andy Shevchenko
2024-10-24 16:15 ` Guenter Roeck
2024-10-24 17:13 ` Ivan Epifanov
2024-10-24 17:18 ` Guenter Roeck
2024-10-24 17:38 ` Ivan Epifanov
2024-10-24 17:28 ` Nopempele N
2024-10-24 17:07 ` Ivan Epifanov
2024-10-24 17:45 ` Sergey Shtylyov
2024-10-25 18:39 ` Tor Vic
[not found] ` <20241024140353.384881-1-vladimir_putin_rus@kremlin.ru>
[not found] ` <20241024140353.384881-2-vladimir_putin_rus@kremlin.ru>
2024-10-30 12:48 ` lore.kernel.org getting senile ? [WAS: [PATCH 1/2] MAINTAINERS: Remove Huawei due to compilance requirements metux
[not found] ` <20241024095339.GA32487@imap.altlinux.org>
2025-10-01 10:11 ` what about CoC? (was: [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements.") Michael Shigorin
2025-10-03 15:48 ` what about CoC? Alexander Lobakin
2025-10-03 16:45 ` Michael Shigorin
[not found] ` <64ef261c-82d0-4fad-ba8a-562f247340fb@metux.net>
2024-10-24 15:33 ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Andy Shevchenko
2024-10-23 8:26 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements Mingcong Bai
2024-10-23 9:38 ` WangYuli
2024-10-23 9:53 ` Jiaxun Yang
2024-10-23 10:10 ` Mingcong Bai
2024-10-23 8:37 ` Mauro Carvalho Chehab
2024-10-23 10:22 ` Nikita Shubin
2024-10-24 15:56 ` [PATCH] MAINTAINERS: Remove some entries due to various moral requirements Enrico Weigelt, metux IT consult
2024-10-26 6:37 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements SekiBetu
2024-10-27 20:20 ` Alexander Pevzner
-- strict thread matches above, loose matches on Subject: below --
2024-10-23 9:50 Anna Antonenko
2024-10-23 10:55 jisralbasha
2024-10-24 11:32 Jensen Huang
2024-10-24 12:34 ` 陈寒彤
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=a520d1f5-8273-d67e-97fe-67f73edce9f1@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox