linux-kernel - Re: [PATCH V4 0/5] mlx5 ConnectX control misc driver

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]

Date: Thu, 4 Apr 2024 20:46:41 +0100
From: Edward Cree <ecree.xilinx@...il.com>
To: Leon Romanovsky <leon@...nel.org>
Cc: Jason Gunthorpe <jgg@...dia.com>, Jakub Kicinski <kuba@...nel.org>,
 David Ahern <dsahern@...nel.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Christoph Hellwig <hch@...radead.org>, Saeed Mahameed <saeed@...nel.org>,
 Arnd Bergmann <arnd@...db.de>, Jiri Pirko <jiri@...dia.com>,
 Leonid Bloch <lbloch@...dia.com>, Itay Avraham <itayavr@...dia.com>,
 Saeed Mahameed <saeedm@...dia.com>,
 Aron Silverton <aron.silverton@...cle.com>, linux-kernel@...r.kernel.org,
 "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
 Andy Gospodarek <andrew.gospodarek@...adcom.com>
Subject: Re: [PATCH V4 0/5] mlx5 ConnectX control misc driver

On 04/04/2024 19:35, Leon Romanovsky wrote:
> On Thu, Apr 04, 2024 at 07:06:53PM +0100, Edward Cree wrote:
>> Why?  What does the kernel get out of it?
>>
>> Maybe *you* need them to be supported, but maybe you should have
>>  thought of that earlier in the design process.  ("A failure on
>>  your part to foresee the eminently foreseeable does not
>>  constitute an emergency on mine.")
>> If we let folks bypass our standards with a _fait accompli_, we
>>  don't really have standards in the first place.
> 
> Sorry, who are "we" and what are "our standards"?

As should be obvious from context, "we" in that sentence referred to
 the mainline kernel.  And while participants in this thread currently
 disagree on what "our standards" are, I hope it is not contentious
 that the kernel community *does* have standards as to what code and
 design is acceptable for inclusion.
Necessarily, for those standards to be meaningful, there cannot be an
 exception for "oh, but we already built our product, it's too late
 now", otherwise everyone would just ignore the standards and then
 demand to be merged anyway.
That is true regardless of the specific standards in question.

> And, please, please reread the thread, it is not about devlink at all.

Please, please, reread the email to which you are replying; it is
 not about devlink at all.

-ed