[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Apr 2024 19:06:53 +0100
From: Edward Cree <ecree.xilinx@...il.com>
To: Jason Gunthorpe <jgg@...dia.com>, Jakub Kicinski <kuba@...nel.org>
Cc: David Ahern <dsahern@...nel.org>, Leon Romanovsky <leon@...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
#include <disclaimer.h>
On 04/04/2024 18:47, Jason Gunthorpe wrote:
> The configurables exist as they are
> and need to be supported, in one way or another, by the kernel.
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.
Powered by blists - more mailing lists