lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <444fa53bdfdee75522a1af41655a99b0@aosc.io>
Date: Wed, 23 Oct 2024 16:26:00 +0800
From: Mingcong Bai <jeffbai@...c.io>
To: WangYuli <wangyuli@...ontech.com>
Cc: gregkh@...uxfoundation.org, patches@...ts.linux.dev, nikita@...n.ru,
 ink@...assic.park.msu.ru, shc_work@...l.ru, richard.henderson@...aro.org,
 mattst88@...il.com, linux-alpha@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, fancer.lancer@...il.com,
 linux-hwmon@...r.kernel.org, dmaengine@...r.kernel.org, xeb@...l.ru,
 netdev@...r.kernel.org, s.shtylyov@....ru, linux-ide@...r.kernel.org,
 serjk@...up.ru, aospan@...up.ru, linux-media@...r.kernel.org,
 ddrokosov@...rdevices.ru, linux-iio@...r.kernel.org, v.georgiev@...rotek.ru,
 linux-mips@...r.kernel.org, ntb@...ts.linux.dev,
 linux-renesas-soc@...r.kernel.org, linux-gpio@...r.kernel.org,
 linux-spi@...r.kernel.org, dushistov@...l.ru,
 manivannan.sadhasivam@...aro.org, conor.dooley@...rochip.com,
 linux-fpga@...r.kernel.org, tsbogend@...ha.franken.de,
 hoan@...amperecomputing.com, geert@...ux-m68k.org,
 wsa+renesas@...g-engineering.com
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various
 compliance requirements.

No, no, no. Nuh, uh.

Greg has unfortunately decided to respond in private over a matter that 
by no means should be glossed over. Here below is our conversation:

---

Greetings,

在 2024-10-23 15:55,Greg KH 写道:

> On Wed, Oct 23, 2024 at 03:32:50PM +0800, Mingcong Bai wrote:
> 
>> Greetings all,
> 
> <offlist>

Request declined. Your response is now public knowledge (and hey, if 
this is not by your will, my apologies). Again, this matter requires 
public response.

> 在 2024-10-23 14:30,WangYuli 写道: Although this commit has been merged, 
> it's still important to know the
> specific reason (or even an example) that triggered this change for
> everyone here, right?
> 
> And those maintainers who have been removed should be notified.
> Seconded.

Sorry, but that's not how this is allowed to work.  Please contact your
company lawyers if you have any questions about this.  And this only
affects maintainers, as you aren't listed in the MAINTAINERS file, there
should not be any issue, but again, contact your company if you have any
questions as they know what is going on.

Just *wink* if you were compelled into this.

> thanks,
> 
> greg k-h

Best Regards,
Mingcong Bai

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ