linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mingcong Bai <jeffbai@aosc.io>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: WangYuli <wangyuli@uniontech.com>,
	gregkh@linuxfoundation.org, patches@lists.linux.dev,
	nikita@trvn.ru, ink@jurassic.park.msu.ru, shc_work@mail.ru,
	richard.henderson@linaro.org, mattst88@gmail.com,
	linux-alpha@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, fancer.lancer@gmail.com,
	linux-hwmon@vger.kernel.org, dmaengine@vger.kernel.org,
	xeb@mail.ru, netdev@vger.kernel.org, s.shtylyov@omp.ru,
	linux-ide@vger.kernel.org, serjk@netup.ru, aospan@netup.ru,
	linux-media@vger.kernel.org, ddrokosov@sberdevices.ru,
	linux-iio@vger.kernel.org, v.georgiev@metrotek.ru,
	linux-mips@vger.kernel.org, ntb@lists.linux.dev,
	linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-spi@vger.kernel.org, dushistov@mail.ru,
	manivannan.sadhasivam@linaro.org, conor.dooley@microchip.com,
	linux-fpga@vger.kernel.org, tsbogend@alpha.franken.de,
	hoan@os.amperecomputing.com, geert@linux-m68k.org,
	wsa+renesas@sang-engineering.com
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements.
Date: Wed, 23 Oct 2024 18:10:14 +0800	[thread overview]
Message-ID: <5d8614084599ff1b7f70aa1b427bdfb3@aosc.io> (raw)
In-Reply-To: <418359de-e084-47f9-9090-7980e41661e0@flygoat.com>

Greetings again (oops),

I messed up the reference levels when I sent my disclosure. Jiaxun got 
most of the references right but the last sentence.

在 2024-10-23 17:53,Jiaxun Yang 写道:
> On 2024/10/23 09:26, Mingcong Bai wrote:
>> 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:
> 
> I can't believe a senior maintainer is breaking our agreed netiquette 
> [1], but that's happening.
> 
>> 在 2024-10-23 15:55,Greg KH 写道:
> [...]
>> 
>> 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.
> 
> I think there are no regulations on earth preventing itself from being 
> referenced.
> Even if the regulation prevents further communication with affected 
> bodies,
> the wider community still deserves an explanation.
> 
> As a person with M entries I found this behavior appalling. It shakes 
> mutual
> trust between maintainers, as we all assumed that patches being applied 
> are
> well scrutinized.
> 
> Besides, many of us are working on kernel as hobbyist  in a personal 
> capacity.
> That means we don't have access to lawyers, especially US one. While I 
> understand
> corporate participants may be the majority of the community, please 
> don't leave
> hobbyists behind!
> 
> I've had some interactions with some of people being removed here, and 
> I would
> say they are all brilliant individuals. It's  really sad to see them 
> being turned away :-(
> 
>> 
>> Just *wink* if you were compelled into this.
> ^ It sounds unprofessional to me.

For the record, I wrote that unprofessional sentence ("Just *wink*"), 
since it was private.

Best Regards,
Mingcong Bai

> 
> Thanks
> - Jiaxun
> 
> [1]: https://people.kernel.org/tglx/notes-about-netiquette-qw89
>> 
>>> thanks,
>>> 
>>> greg k-h
>> 
>> Best Regards,
>> Mingcong Bai
>> 

  reply	other threads:[~2024-10-23 10:10 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024101835-tiptop-blip-09ed@gregkh>
2024-10-23  6:30 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements WangYuli
2024-10-23  7:32   ` Mingcong Bai
2024-10-23  8:09     ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Kexy Biscuit
2024-10-23  8:26       ` Nikita Travkin
2024-10-23  8:35         ` WangYuli
2024-10-23  9:04       ` Mingcong Bai
2024-10-23  9:28       ` Tonghao Zhang
2024-10-23 10:27       ` Nikita Shubin
2024-10-23 14:47       ` Lance Yang
2024-10-23 15:03       ` Yangyu Chen
2024-10-23 15:04       ` Sergio Paracuellos
2024-10-23 16:22       ` Yao Zi
2024-10-23 16:51       ` Tor Vic
2024-10-23 17:45         ` Linus Torvalds
2024-10-23 18:56           ` Phillip Susi
2024-10-23 19:15           ` Peter Cai
2024-10-23 19:19             ` Linus Torvalds
2024-10-23 19:28               ` Peter Cai
2024-10-24 21:01               ` Mikhail Novosyolov
2024-10-25  7:11                 ` Nikolay Kichukov
2024-10-23 19:50           ` Tor Vic
2024-10-23 22:14           ` NotYourFox
2024-10-24  7:11           ` Integral
     [not found]           ` <20241024095708.189649-1-isage.dna@gmail.com>
2024-10-24 15:41             ` Andy Shevchenko
2024-10-24 16:15               ` Guenter Roeck
2024-10-24 17:13                 ` Ivan Epifanov
2024-10-24 17:18                   ` Guenter Roeck
2024-10-24 17:38                     ` Ivan Epifanov
2024-10-24 17:28                 ` Nopempele N
2024-10-24 17:07               ` Ivan Epifanov
2024-10-24 17:45                 ` Sergey Shtylyov
2024-10-25 18:39           ` Tor Vic
     [not found]           ` <20241024140353.384881-1-vladimir_putin_rus@kremlin.ru>
     [not found]             ` <20241024140353.384881-2-vladimir_putin_rus@kremlin.ru>
2024-10-30 12:48               ` lore.kernel.org getting senile ? [WAS: [PATCH 1/2] MAINTAINERS: Remove Huawei due to compilance requirements metux
     [not found]       ` <64ef261c-82d0-4fad-ba8a-562f247340fb@metux.net>
2024-10-24 15:33         ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Andy Shevchenko
2024-10-23  8:26     ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements Mingcong Bai
2024-10-23  9:38       ` WangYuli
2024-10-23  9:53       ` Jiaxun Yang
2024-10-23 10:10         ` Mingcong Bai [this message]
2024-10-23 10:22 ` Nikita Shubin
2024-10-24 11:32 Jensen Huang
2024-10-24 12:34 ` 陈寒彤
  -- strict thread matches above, loose matches on Subject: below --
2024-10-23 10:55 jisralbasha
2024-10-23  9:50 Anna Antonenko

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=5d8614084599ff1b7f70aa1b427bdfb3@aosc.io \
    --to=jeffbai@aosc.io \
    --cc=aospan@netup.ru \
    --cc=conor.dooley@microchip.com \
    --cc=ddrokosov@sberdevices.ru \
    --cc=dmaengine@vger.kernel.org \
    --cc=dushistov@mail.ru \
    --cc=fancer.lancer@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hoan@os.amperecomputing.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mattst88@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikita@trvn.ru \
    --cc=ntb@lists.linux.dev \
    --cc=patches@lists.linux.dev \
    --cc=richard.henderson@linaro.org \
    --cc=s.shtylyov@omp.ru \
    --cc=serjk@netup.ru \
    --cc=shc_work@mail.ru \
    --cc=tsbogend@alpha.franken.de \
    --cc=v.georgiev@metrotek.ru \
    --cc=wangyuli@uniontech.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=xeb@mail.ru \
    /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).