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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025022221-aviation-rectangle-c497@gregkh>
Date: Sat, 22 Feb 2025 14:57:43 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Hillf Danton <hdanton@...a.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
	Matthew Wilcox <willy@...radead.org>,
	Byungchul Park <byungchul@...com>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, conduct@...nel.org
Subject: Re: [RFC PATCH v12 00/26] LUF(Lazy Unmap Flush) reducing tlb numbers
 over 90%

On Sat, Feb 22, 2025 at 06:10:59PM +0800, Hillf Danton wrote:
> On Sat, 22 Feb 2025 08:16:09 +0100 Greg KH <gregkh@...uxfoundation.org>
> > On Sat, Feb 22, 2025 at 07:05:26AM +0800, Hillf Danton wrote:
> > > On Thu, 20 Feb 2025 18:44:12 -0500 Steven Rostedt <rostedt@...dmis.org>
> > > > On Fri, 21 Feb 2025 07:25:02 +0800 Hillf Danton <hdanton@...a.com> wrote:
> > > > > > I'll tell you what would happen in my home town. If someone said
> > > > > > that to a co-worker, they would likely be terminated.
> > > > > >   
> > > > > Interesting, I want to know if the three words, rape, pregnancy and WTK,
> > > > > could be used before judge in your hometown court by anyone like your lawyer.
> > > > 
> > > > This isn't a court. And there's no reason to use the word "rape" in a
> > > > technical conversation on the Linux kernel mailing list. Perhaps a person
> > > > reading this was a victim of rape. How do you think that would make them
> > > > feel? Welcomed to our community? Absolutely not. Which is why it's totally
> > > > unacceptable.
> > > > 
> > > There are NAK victims. Did you nak more than twice a week, Steve?
> > 
> > This is not the way to work with your fellow developers in the community
> > to express disagreements.
> >
> No comment because you are free to express disagreements.

Disagreements are fine, but not with words like what you used, sorry,
that was unacceptable and requires an apology.

> > I would recommend following up with an apology.
> > 
> It would take some time for me to opt to follow/ignore what you recommended.

Please take the time to do so very soon.

thanks,

greg k-h (On behalf of the Code of Conduct Committee)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ