From: "Theodore Ts'o" <tytso@mit.edu>
To: quake <quake.wang@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove Huawei
Date: Thu, 24 Oct 2024 12:49:39 -0400 [thread overview]
Message-ID: <20241024164939.GL3204734@mit.edu> (raw)
In-Reply-To: <20241024032637.34286-1-quake.wang@gmail.com>
On Thu, Oct 24, 2024 at 12:26:37PM +0900, quake wrote:
> From: Quake Wang <quake.wang@gmail.com>
>
> Remove some entries due to various compliance requirements. They
> cannot come back in the future as huawei is sanctioned by most
> freedom countries in the world.
Note that there are multiple sanction regimes and exactly what the
rules are vary from country to country. At least in the US there are
exemptions that mean that I can accept patches and send code reviews
for engineers from Huawei so long as they occur in a public forum,
such as the LKML mailing lists. As a result, folks may have noticed
that there are ext4 patches from Huawei, and I personally consider
them very valuable contributors to the ext4 community.
These exemptions may not apply in different countries, and for
different sanctioned entities. I will note that China is not
currently attacking Taiwan militarily at the moment, while Russian
misiles and drones, some of which might be using embedded Linux
controllers, *are* actively attacking another country even as we
speak. So it might not be surprising that the rules might be
different for different sanctioned entities.
Finally, please remember that kernel developers don't make the rules.
Those laws are made by the US, European, Japanese, and other
governments. My personal priorites are to make sure that *I* don't
run afoul of any local civil or criminal penalties, and to make sure
that other Linux developers can also stay safe. That being said, I'm
not a lawyer, and so please don't take anything I say as legal advice.
What I'm comfortable doing as the ext4 maintainer living in the US
might not be applicable for someone else who might have different
circumstances.
So for example, it could very much be the case that other countries
have *stricter* laws, and if you are acting as a maintainer, in terms
of accepting other people's code, or providing design guidance (which
may be considered "providing technical assistance" in some countries'
laws) --- if you are uncertain, please reach out to a lawyer.
- Ted
P.S. This has always been the case, even before one country invaded
another; maintainers take on real legal responsibilities as part of
their work. It's just that the consequences of copyright and patent
issues were much less than when there are sanctions involving
countries who are actively at war with others.
next prev parent reply other threads:[~2024-10-24 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 3:26 [PATCH] Remove Huawei quake
2024-10-24 3:38 ` Dragan Milivojević
2024-10-24 5:13 ` Quake Wang
[not found] ` <CAJkr5LNm=fm1rzOv9z3V6c0N=6QM3ngmYGHjniAvJAY__n5KYQ@mail.gmail.com>
2024-10-24 17:29 ` Dragan Milivojević
2024-10-24 16:49 ` Theodore Ts'o [this message]
2024-10-24 17:26 ` Dragan Milivojević
2024-10-30 13:17 ` Politware vs Free Software [WAS [PATCH] Remove Huawei] metux
2024-11-04 3:29 ` Morozov
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=20241024164939.GL3204734@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=quake.wang@gmail.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