netdev - Re: what about CoC?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87371abc-e43f-4afb-83d0-b9a04fc015c0@intel.com>
Date: Fri, 3 Oct 2025 17:48:40 +0200
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Michael Shigorin <mike@...linux.org>, Michael Shigorin <mike@...linux.ru>
CC: Linus Torvalds <torvalds@...ux-foundation.org>, Tor Vic
	<torvic9@...lbox.org>, Kexy Biscuit <kexybiscuit@...c.io>, <jeffbai@...c.io>,
	<gregkh@...uxfoundation.org>, <wangyuli@...ontech.com>, <aospan@...up.ru>,
	<conor.dooley@...rochip.com>, <ddrokosov@...rdevices.ru>,
	<dmaengine@...r.kernel.org>, <dushistov@...l.ru>, <fancer.lancer@...il.com>,
	<geert@...ux-m68k.org>, <hoan@...amperecomputing.com>,
	<ink@...assic.park.msu.ru>, <linux-alpha@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <linux-fpga@...r.kernel.org>,
	<linux-gpio@...r.kernel.org>, <linux-hwmon@...r.kernel.org>,
	<linux-ide@...r.kernel.org>, <linux-iio@...r.kernel.org>,
	<linux-media@...r.kernel.org>, <linux-mips@...r.kernel.org>,
	<linux-renesas-soc@...r.kernel.org>, <linux-spi@...r.kernel.org>,
	<manivannan.sadhasivam@...aro.org>, <mattst88@...il.com>,
	<netdev@...r.kernel.org>, <nikita@...n.ru>, <ntb@...ts.linux.dev>,
	<patches@...ts.linux.dev>, <richard.henderson@...aro.org>,
	<s.shtylyov@....ru>, <serjk@...up.ru>, <shc_work@...l.ru>,
	<tsbogend@...ha.franken.de>, <v.georgiev@...rotek.ru>,
	<wsa+renesas@...g-engineering.com>, <xeb@...l.ru>
Subject: Re: what about CoC?

From: Michael Shigorin <mike@...linux.org>
Date: Wed, 1 Oct 2025 13:11:48 +0300

> On Thu, Oct 24, 2024 at 12:53:39PM +0300, I wrote
>> It's not about the patch but rather about the attitude;
>> Documentation/process/code-of-conduct-interpretation.rst:
>>
>> "regardless of ... ethnicity, ... nationality, ... race"

Lemme necro-post as well and insert my 2 coins here, for those who still
yell "it's all about ethnicity!!1".

No it's not. It's about companies that sponsor the war or are a part of it.

I wouldn't exaggerate if I say that at least a good half of Russian IT
and HW is dual-purpose / gov-owned if not most of it.

You want to talk about poor Baikal? It was under sanctions even back in
2013 before the Crimea events for being dual-purpose and ARM refused to
give them the license, so they fell back to MIPS.

Most, if not all, Russian Linux distributions are used by the govs AND
military.

So banning the `.ru` domain etc. on LKML would be like 90% precise shot
and 10% collateral damage which is a fair ratio nevertheless.
I'd rather reject a patch than get a rocket in my face powered by this
patch. Even if it's "focused on what is best for the community".

Instead of citing the Code of Conduct and all that stuff, refer to the
kernel documentation about the international restrictions for certain
HW/countries/purposes (including dual).

>> "Focusing on what is best for the community"
>>
>> "Examples of unacceptable behavior ... insulting/derogatory
>> comments ... Public or private harassment"
>>
>> Get back to single-standard integrity for yor own's sake.
Thanks,
Olek