From: "Theodore Ts'o" <tytso@mit.edu>
To: Hantong Chen <cxwdyx620@gmail.com>
Cc: james.bottomley@hansenpartnership.com, ajhalaney@gmail.com,
allenbh@gmail.com, andrew@lunn.ch,
andriy.shevchenko@linux.intel.com, andy@kernel.org,
arnd@arndb.de, bhelgaas@google.com, bp@alien8.de,
broonie@kernel.org, cai.huoqing@linux.dev, dave.jiang@intel.com,
davem@davemloft.net, dlemoal@kernel.org,
dmaengine@vger.kernel.org, dushistov@mail.ru,
fancer.lancer@gmail.com, geert@linux-m68k.org,
gregkh@linuxfoundation.org, ink@jurassic.park.msu.ru,
jdmason@kudzu.us, jiaxun.yang@flygoat.com,
keguang.zhang@gmail.com, kory.maincent@bootlin.com,
krzk@kernel.org, kuba@kernel.org, linux-edac@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-serial@vger.kernel.org, linux-spi@vger.kernel.org,
linux@armlinux.org.uk, linux@roeck-us.net,
manivannan.sadhasivam@linaro.org, netdev@vger.kernel.org,
nikita.shubin@maquefel.me, nikita@trvn.ru, ntb@lists.linux.dev,
olteanv@gmail.com, pabeni@redhat.com, paulburton@kernel.org,
robh@kernel.org, s.shtylyov@omp.ru, sergio.paracuellos@gmail.com,
shc_work@mail.ru, siyanteng@loongson.cn,
tsbogend@alpha.franken.de, xeb@mail.ru,
yoshihiro.shimoda.uh@renesas.com
Subject: Re: linux: Goodbye from a Linux community volunteer
Date: Thu, 24 Oct 2024 13:35:04 -0400 [thread overview]
Message-ID: <20241024173504.GN3204734@mit.edu> (raw)
In-Reply-To: <20241024165650.174-1-cxwdyx620@gmail.com>
On Thu, Oct 24, 2024 at 04:56:50PM +0000, Hantong Chen wrote:
>
> For People???s Republic of China, there are about 500 entities that
> are on the U.S. OFAC SDN / non-SDN lists, especially HUAWEI, which
> is one of the most active employers from versions 5.16 through 6.1,
> according to statistics. This is unacceptable, and we must take
> immediate action to address it, with the **same** reason.
There are multiple sanctions programs, and at least in the US, for the
sanctions program which Huawei is in, there is an exception for
conversations and patches that take place in a public mailing list,
such as LKML. As a result, as the ext4 maintainer, I am comfortable
taking patches from engineers employed by Huawei, and I consider them
valued members of the ext4 development community.
However, note that China is *not* actively attacking Taiwai
militarily, while there are Russian missiles and drones, some of which
may controlled by embedded Linux systems, that are being used against
Ukraine even as we speak. Hence, it should not be surprising that the
rules imposed by the US Government might be different for Huawei
compared to other sanctioned entities that are directly or indirectly
controlled by the Russian Military-Industrial complex.
There are also other sanctions regimes imposed by Japan, European
Countries, etc., which might be more or less strict. So in general,
if you are not sure what you need to do as an US, European, Japanese,
etc. citizen who might be subject to civil or criminal penalties ----
talk to a lawyer.
The bottom line is that it is a false equivalence to claim that
sanctions involving China and Russia are the same. They very much
aren't; one country is engaging in an active shooting war (or if you
prefer, "special military operation"), and the other is not.
Of course, if China were to militarily attack Taiwan or some other
country in Asia, circumstances might change at some point in the
future. Hopefully Chinese leaders will pursue a path of wisdom and
those consequences won't come to pass. Ultimately, though, that's not
up to any of us on this mail thread.
Cheers,
- Ted
next prev parent reply other threads:[~2024-10-24 17:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 4:27 linux: Goodbye from a Linux community volunteer Serge Semin
2024-10-24 6:55 ` Reimar Döffinger
2024-10-24 7:32 ` Philipp Stanner
2024-10-24 11:01 ` Jiaxun Yang
2024-10-24 14:50 ` James Bottomley
2024-10-24 15:59 ` Jiaxun Yang
2024-10-24 16:18 ` Dragan Milivojević
2024-10-24 16:27 ` James Bottomley
2024-10-24 16:58 ` Jiaxun Yang
2024-10-25 7:59 ` Andreas Herrmann
2024-10-24 16:30 ` Peter Cai
2024-10-24 17:18 ` Dragan Milivojević
2024-10-24 17:59 ` Andy Shevchenko
2024-10-24 19:46 ` Dragan Milivojević
2024-10-25 13:12 ` Andy Shevchenko
2024-10-30 14:40 ` metux
[not found] ` <6d37175d-1b0b-4b82-80f0-c5b4e61badbf@metux.net>
[not found] ` <2f12ee89-af9f-4af1-8ec8-ede1d5256592@metux.net>
[not found] ` <CALtW_agiJyX3sTaBKgwPF7X920=+fFrRgXMPt4x_GCDOMfZy_w@mail.gmail.com>
[not found] ` <CALtW_aimN531aZKSSG4hVLeQDk6bUoujopkhCh57xsaxfJrYgA@mail.gmail.com>
2024-10-30 13:48 ` Kernel maintainer *CENSORED* on LKML [WAS: linux: Goodbye from a Linux community volunteer] metux
2024-10-30 14:54 ` Goran
[not found] ` <CALtW_ah07h7h6eNHHGNNeKzVkNi7hVOG3q4Pv9DNacpXgve5Sw@mail.gmail.com>
2024-10-30 18:32 ` metux
2024-10-30 15:05 ` metux
2024-10-24 17:33 ` linux: Goodbye from a Linux community volunteer Jiaxun Yang
2024-10-24 16:56 ` Hantong Chen
2024-10-24 17:35 ` Theodore Ts'o [this message]
2024-10-24 18:19 ` Hantong Chen
2024-10-24 19:37 ` Theodore Ts'o
2024-10-24 20:01 ` Dragan Milivojević
[not found] ` <e3559794-ab4a-48f2-8c28-52ef46258051@metux.net>
2024-10-30 15:02 ` Maintainers now blocked from kernel.org mail access [WAS Re: linux: Goodbye from a Linux community volunteer] metux
[not found] ` <cc264780-0c16-4209-8736-ada156994eaa@metux.net>
2024-10-25 15:18 ` linux: Goodbye from a Linux community volunteer Theodore Ts'o
2024-10-24 18:52 ` Oleksiy Protas
2024-10-24 19:51 ` Dragan Milivojević
2024-10-25 3:01 ` Oleksiy Protas
2024-10-25 13:19 ` Andy Shevchenko
2024-10-25 16:10 ` Oleksiy Protas
2024-10-25 6:48 ` Khalil Fazal
2024-10-30 1:49 ` Yanteng Si
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=20241024173504.GN3204734@mit.edu \
--to=tytso@mit.edu \
--cc=ajhalaney@gmail.com \
--cc=allenbh@gmail.com \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=cxwdyx620@gmail.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=dlemoal@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dushistov@mail.ru \
--cc=fancer.lancer@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=james.bottomley@hansenpartnership.com \
--cc=jdmason@kudzu.us \
--cc=jiaxun.yang@flygoat.com \
--cc=keguang.zhang@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
--cc=nikita@trvn.ru \
--cc=ntb@lists.linux.dev \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=paulburton@kernel.org \
--cc=robh@kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=sergio.paracuellos@gmail.com \
--cc=shc_work@mail.ru \
--cc=siyanteng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--cc=xeb@mail.ru \
--cc=yoshihiro.shimoda.uh@renesas.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).