Update MAINTAINERS

[quake]

Follow 6e90b67, 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.

--- update ---
To all down voters:

If you haven't heard of huawei sanctions yet, you should try to read the news some day. And by "news", I don't mean China state-sponsored spam.

[KernelPRBot]

Hi @quake!

Thanks for your contribution to the Linux kernel!

Linux kernel development happens on mailing lists, rather than on GitHub - this GitHub repository is a read-only mirror that isn't used for accepting contributions. So that your change can become part of Linux, please email it to us as a patch.

Sending patches isn't quite as simple as sending a pull request, but fortunately it is a well documented process.

Here's what to do:

• Format your contribution according to kernel requirements
• Decide who to send your contribution to
• Set up your system to send your contribution as an email
• Send your contribution and wait for feedback

How do I format my contribution?

The Linux kernel community is notoriously picky about how contributions are formatted and sent. Fortunately, they have documented their expectations.

Firstly, all contributions need to be formatted as patches. A patch is a plain text document showing the change you want to make to the code, and documenting why it is a good idea.

You can create patches with git format-patch.

Secondly, patches need 'commit messages', which is the human-friendly documentation explaining what the change is and why it's necessary.

Thirdly, changes have some technical requirements. There is a Linux kernel coding style, and there are licensing requirements you need to comply with.

Both of these are documented in the Submitting Patches documentation that is part of the kernel.

Note that you will almost certainly have to modify your existing git commits to satisfy these requirements. Don't worry: there are many guides on the internet for doing this.

Where do I send my contribution?

The Linux kernel is composed of a number of subsystems. These subsystems are maintained by different people, and have different mailing lists where they discuss proposed changes.

If you don't already know what subsystem your change belongs to, the get_maintainer.pl script in the kernel source can help you.

get_maintainer.pl will take the patch or patches you created in the previous step, and tell you who is responsible for them, and what mailing lists are used. You can also take a look at the MAINTAINERS file by hand.

Make sure that your list of recipients includes a mailing list. If you can't find a more specific mailing list, then LKML - the Linux Kernel Mailing List - is the place to send your patches.

It's not usually necessary to subscribe to the mailing list before you send the patches, but if you're interested in kernel development, subscribing to a subsystem mailing list is a good idea. (At this point, you probably don't need to subscribe to LKML - it is a very high traffic list with about a thousand messages per day, which is often not useful for beginners.)

How do I send my contribution?

Use git send-email, which will ensure that your patches are formatted in the standard manner. In order to use git send-email, you'll need to configure git to use your SMTP email server.

For more information about using git send-email, look at the Git documentation or type git help send-email. There are a number of useful guides and tutorials about git send-email that can be found on the internet.

How do I get help if I'm stuck?

Firstly, don't get discouraged! There are an enormous number of resources on the internet, and many kernel developers who would like to see you succeed.

Many issues - especially about how to use certain tools - can be resolved by using your favourite internet search engine.

If you can't find an answer, there are a few places you can turn:

• Kernel Newbies - this website contains a lot of useful resources for new kernel developers.
• The kernel documentation - see also the Documentation directory in the kernel tree.

If you get really, really stuck, you could try the owners of this bot, @daxtens and @ajdlinux. Please be aware that we do have full-time jobs, so we are almost certainly the slowest way to get answers!

I sent my patch - now what?

You wait.

You can check that your email has been received by checking the mailing list archives for the mailing list you sent your patch to. Messages may not be received instantly, so be patient. Kernel developers are generally very busy people, so it may take a few weeks before your patch is looked at.

Then, you keep waiting. Three things may happen:

• You might get a response to your email. Often these will be comments, which may require you to make changes to your patch, or explain why your way is the best way. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
• Your patch might be merged into the subsystem tree. Code that becomes part of Linux isn't merged into the main repository straight away - it first goes into the subsystem tree, which is managed by the subsystem maintainer. It is then batched up with a number of other changes sent to Linus for inclusion. (This process is described in some detail in the kernel development process guide).
• Your patch might be ignored completely. This happens sometimes - don't take it personally. Here's what to do:
  • Wait a bit more - patches often take several weeks to get a response; more if they were sent at a busy time.
  • Kernel developers often silently ignore patches that break the rules. Check for obvious violations of the Submitting Patches guidelines, the style guidelines, and any other documentation you can find about your subsystem. Check that you're sending your patch to the right place.
  • Try again later. When you resend it, don't add angry commentary, as that will get your patch ignored. It might also get you silently blacklisted.

Further information

• Working with the kernel development community - the official documentation for new kernel contributors

Happy hacking!

This message was posted by a bot - if you have any questions or suggestions, please talk to my owners, @ajdlinux and @daxtens, or raise an issue at https://github.com/ajdlinux/KernelPRBot.

[as181920]

The correct way is to revert the commit 6e90b67

don't let the mistake get worse.

[gulprun]

The decision to remove maintainers based on their .ru email domains is both impractical and problematic. It doesn’t account for all Russian contributors, as not all use .ru domains, and it sets a concerning precedent for potentially targeting other developers in the future.

For instance, if the geopolitical situation worsens, distinguishing Chinese developers could become similarly difficult, given that many don’t use .cn email addresses. Such actions risk fragmenting the open-source community. If this policy was deemed necessary, it should have been accompanied by clear and transparent communication to the affected developers and the community at large. Without that, it feels more like a symbolic move than a constructive one.

[Miracle05]

Can you explain "various compliance requirements"?

[RinLin-NYA]

That's not enough.
We should remove any contributors who come from Russia, China(with HongKong Macau), South Africa, Iran, Syria, Yemen, Iraq, Algeria, Afghanistan, Pakistan, Jordan, Egypt, Liberia, Cuba, Venezuela and any other Countries or Regions exclude West Europe and North America lol

---

This is just a joke, btw why so~~~~~ many people really in favor to this?

[armv7a]

🤣🤣🤣🤣

[NorthernBlow]

you should use git revert

[NorthernBlow]

Not enough has been done to break up the opensource community. you have a lot of work ahead of you.

[ForkKILLET]

lgtm

[chenyingchun0312]

This PR should be closed!

[Dongtianze]

lol nice try

[another1024]

That's not enough.
We should remove any code which come from Russia, China(with HongKong Macau), South Africa, Iran, Syria, Yemen, Iraq, Algeria, Afghanistan, Pakistan, Jordan, Egypt, Liberia, Cuba, Venezuela and any other Countries or Regions exclude West Europe and North America

[eadechan]

power lol

[m0n203]

What's next?
Black people? Females? LGBTQ?
Are we still in 21st century?

[alex3236]

u know what, i think we should remove any codes that are made outside of the US

[ShEpic]

@quake These actions are discrimination on the basis of nationality and racism, support for sanctions that are illegal in circumvention of the UN, accordingly I have filed a complaint against you, which will definitely be considered.

[M1NGS]

well done, but you forgot something such as Hikvision, DJI, ZTE, Bytedance, kylix linux......

[happysmile12321]

[Butterblock233]

[happysmile12321]

MAKE VV GREAT AGAIN!!!

[dalongxia2017]

[kmou424]

[Butterblock233]

[RyrieNorth]

Child, this burden is far too heavy for you to bear.

[n1vk]

I suggest removing all ".com" emails to ensure that the open-source community is not influenced by any COMpany

[Butterblock233]

[quake]

To all down voters:

If you haven't heard of huawei sanctions yet, you should try to read the news some day. And by "news", I don't mean China state-sponsored spam.

[happysmile12321]

遵循 6e90b67，由于各种合规性要求，删除了一些条目。他们将来不能回来，因为华为受到世界上大多数自由国家的制裁。

---更新---致所有落选的选民：

如果您还没有听说过华为的制裁，您应该有一天尝试阅读新闻。我所说的“新闻”，我不是指中国国家支持的垃圾邮件。

Bug Yellow!

[happysmile12321]

bug yellow

[Justjustifyjudge]

VV不削能玩？

[Justjustifyjudge]

我的评价是:200个贡献者里面抓出来了180个俄罗斯巨魔是吧，那我只能称赞Linus Benedict Torvalds先生如同许世友将军一样能文能武，技术十分优秀，然后进行多快好省的fork。开源社区不灭，不过分裂罢了。

能能能能，技术十分英俊👍

[FreeOfVirtue]

我的评价是:200个贡献者里面抓出来了180个俄罗斯巨魔是吧，那我只能称赞Linus Benedict Torvalds先生如同许世友将军一样能文能武，技术十分优秀，然后进行多快好省的fork。开源社区不灭，不过分裂罢了。

能能能能，技术十分英俊👍

不过要是在中国，Linus不符合那些制裁管理规定恐怕就要，享受王洪文一样的待遇了吧。
MSS恐怕就要说:
最大恶极的林那斯泄露了9207个国家机密，植入了1133个漏洞，骗取了5295元国家援助，铺张浪费的购买了525个电脑，违法了5841次，浪费了电660度，同意了1000次恶意代码提交吧。

[aarpro]

That's not enough. We should remove any code which come from Russia, China(with HongKong Macau), South Africa, Iran, Syria, Yemen, Iraq, Algeria, Afghanistan, Pakistan, Jordan, Egypt, Liberia, Cuba, Venezuela and any other Countries or Regions exclude West Europe and North America

Don't tell them what to do.

[michael-eddy]

我只是好奇。相关开发人员已从 MAINTAINERS 中删除，未添加到 CREDITS 中。这个行为不是违反了 GPL-v2 许可证吗？

GPL=狗屁了，make sence

[FreeOfVirtue]

我只是好奇。相关开发人员已从 MAINTAINERS 中删除，未添加到 CREDITS 中。这个行为不是违反了 GPL-v2 许可证吗？

GPL=狗屁了，make sence

GPL协议的基础是遵守美国法律，这事情的法律依据是ofac制裁名单，自然不违反了。

[michael-eddy]

我只是好奇。相关开发人员已从 MAINTAINERS 中删除，未添加到 CREDITS 中。这个行为不是违反了 GPL-v2 许可证吗？

GPL=狗屁了，make sence

GPL协议的基础是遵守美国法律，这事情的法律依据是ofac制裁名单，自然不违反了。

根据第8条是吧（笑

[black23eep]

idiot

[chemio9]

genius!

[mikhailal]

Kind reminder on this PR.

Why it has not been merged to master yet? How's progress? I expected we were living in such a democratic world of equal opportunities for everyone, but they ban Linux kernel maintainers after quick look on their emails.

The laws and regulations should be equal for everyone? Or what? Maybe somebody's business depends on conjuncture and money? What should you do, linus?

[Wolffyhtl]

Code is cheap,
show me your nationality

[57ar7up-3]

• 支持你的想法的言论自由 = 言论自由
• 指出你的错误的言论自由 = 垃圾邮件
• “反对”你的某些观点的言论自由 = 付费演员
• Freedom of speech that support your idea = Freedom of speech
• Freedom of speech that point out your mistake = Spam
• Freedom of speech that "against" some of your opinion = Paid actor

I thought you have your own internet in asia, no?

[ChenYun10]

我只是好奇。相关开发人员已从 MAINTAINERS 中删除，未添加到 CREDITS 中。这个行为不是违反了 GPL-v2 许可证吗？

GPL=狗屁了，make sence

GPL协议的基础是遵守美国法律，这事情的法律依据是ofac制裁名单，自然不违反了。

不做评价（笑哭）

[0x44614D696E67]

6 啊买瑞卡特有的 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

…

________________________________ 发件人: Chen Yun ***@***.***> 发送时间: Thursday, December 26, 2024 11:05:30 AM 收件人: torvalds/linux ***@***.***> 抄送: 0x44614D696E67 ***@***.***>; Comment ***@***.***> 主题: Re: [torvalds/linux] Update MAINTAINERS (PR #988) 我只是好奇。相关开发人员已从 MAINTAINERS 中删除，未添加到 CREDITS 中。这个行为不是违反了 GPL-v2 许可证吗？ GPL=狗屁了，make sence GPL协议的基础是遵守美国法律，这事情的法律依据是ofac制裁名单，自然不违反了。 不做评价（笑哭） ― Reply to this email directly, view it on GitHub<#988 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXNRY5VTM7K7YOSI6RRDYRL2HNW7VAVCNFSM6AAAAABQOW4YBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRSGEYDKMZYGU>. You are receiving this because you commented.Message ID: ***@***.***>

[ChenYun10]

It's not that there is no need to be obsessed with such a thing right now, whether it is political or otherwise, it really has little to do with us, although I am saying it selfishly, but it is true> >

• 支持你的想法的言论自由 = 言论自由
• 指出你的错误的言论自由 = 垃圾邮件
• “反对”你的某些观点的言论自由 = 付费演员
• Freedom of speech that support your idea = Freedom of speech
• Freedom of speech that point out your mistake = Spam
• Freedom of speech that "against" some of your opinion = Paid actor

I thought you have your own internet in asia, no?

[FreeOfVirtue]

得，美利坚合众国也开始建造属于自己的网络长城喽。威斯特伐利亚体系的触角在深入互联网之后就是毁灭互联网，更是要消灭开源之火，或许威斯特伐利亚的触角们用的还是许多开源技术。
我觉得已经没有给开源项目贡献代码的必要了，不要打白工，更不要自我跌价。

[yanboishere]

LOL

Although as a Chinese I don't like Huawei, what I want to say is that you should never associate the code and the contributions of open sourcers with political backgrounds.

This has become particularly evident since Covid19. I hope the administrator will close this PR.

This behavior is tantamount to clown.

🤡

[yanboishere]

哎 每周看Linux的PR评论区都能被乐到

[yanboishere]

刚发现提PR的这个哥们是CKB的核心贡献者

"赞的 还是中心化好"

[Daiyangcheng]

还有高手？

[BETTEY-developers]

还有高手？lol

[Lingxiiiw]

还有高手？

[Lingxiiiw]

还有高手？

[fuydg]

还有高手？

[Agape2077]

怎么腾讯云拉了拖大的还能让这边多两条回复的？

Why are there some replies when TencentCloud makes trouble?