From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: Kexy Biscuit <kexybiscuit@aosc.io>
Cc: jeffbai@aosc.io, gregkh@linuxfoundation.org,
wangyuli@uniontech.com, torvalds@linux-foundation.org,
aospan@netup.ru, conor.dooley@microchip.com,
ddrokosov@sberdevices.ru, dmaengine@vger.kernel.org,
dushistov@mail.ru, fancer.lancer@gmail.com,
geert@linux-m68k.org, hoan@os.amperecomputing.com,
ink@jurassic.park.msu.ru, linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-fpga@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-ide@vger.kernel.org,
linux-iio@vger.kernel.org, linux-media@vger.kernel.org,
linux-mips@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-spi@vger.kernel.org, manivannan.sadhasivam@linaro.org,
mattst88@gmail.com, netdev@vger.kernel.org, nikita@trvn.ru,
ntb@lists.linux.dev, patches@lists.linux.dev,
richard.henderson@linaro.org, s.shtylyov@omp.ru, serjk@netup.ru,
shc_work@mail.ru, tsbogend@alpha.franken.de,
v.georgiev@metrotek.ru, wsa+renesas@sang-engineering.com,
xeb@mail.ru
Subject: Re: [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements."
Date: Wed, 23 Oct 2024 17:04:47 +0200 [thread overview]
Message-ID: <CAMhs-H_2tnpeynm2m9KNGL1GVU9m+odSnTk6F-WKLruMfEjXUg@mail.gmail.com> (raw)
In-Reply-To: <20241023080935.2945-2-kexybiscuit@aosc.io>
On Wed, Oct 23, 2024 at 10:20 AM Kexy Biscuit <kexybiscuit@aosc.io> wrote:
>
> This reverts commit 6e90b675cf942e50c70e8394dfb5862975c3b3b2.
>
> An absolutely no-one-ever-reviewed patch, not even by the maintainers who
> got removed themselves - at least not on the mailing list. Then the patch
> just got slipped into an unrelated subsystem pull request, and got pulled
> by Torvalds with not even a comment.
>
> What about the next time? Who next would be removed from the MAINTAINERS
> file, the kernel.org infrastructure? What if the compliance requires
> another XZ backdoor to be developed without further explanation? Is the
> kernel development process still done in public?
>
> Are the "compliance requirements" documented on docs.kernel.org? Who are
> responsible for them? Are all that are responsible employees of
> The Linux Foundation, which is regulated by the U.S. legislature?
>
> Fixes: 6e90b675cf94 ("MAINTAINERS: Remove some entries due to various compliance requirements.")
> Signed-off-by: Kexy Biscuit <kexybiscuit@aosc.io>
> ---
Unbelievable...
Acked-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Thanks,
Sergio Paracuellos
next prev parent reply other threads:[~2024-10-23 15:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024101835-tiptop-blip-09ed@gregkh>
2024-10-23 6:30 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements 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:03 ` Yangyu Chen
2024-10-23 15:04 ` Sergio Paracuellos [this message]
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 10:22 ` Nikita Shubin
2024-10-25 8:46 [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." thomas superb
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=CAMhs-H_2tnpeynm2m9KNGL1GVU9m+odSnTk6F-WKLruMfEjXUg@mail.gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=aospan@netup.ru \
--cc=conor.dooley@microchip.com \
--cc=ddrokosov@sberdevices.ru \
--cc=dmaengine@vger.kernel.org \
--cc=dushistov@mail.ru \
--cc=fancer.lancer@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hoan@os.amperecomputing.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jeffbai@aosc.io \
--cc=kexybiscuit@aosc.io \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mattst88@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=ntb@lists.linux.dev \
--cc=patches@lists.linux.dev \
--cc=richard.henderson@linaro.org \
--cc=s.shtylyov@omp.ru \
--cc=serjk@netup.ru \
--cc=shc_work@mail.ru \
--cc=torvalds@linux-foundation.org \
--cc=tsbogend@alpha.franken.de \
--cc=v.georgiev@metrotek.ru \
--cc=wangyuli@uniontech.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=xeb@mail.ru \
/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).