[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7dcdd0ba-e7f8-4aa8-a551-8c0ab4c51cd9@intel.com>
Date: Wed, 10 Apr 2024 15:03:54 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Jakub Kicinski <kuba@...nel.org>, Florian Fainelli <f.fainelli@...il.com>
CC: Alexander Duyck <alexander.duyck@...il.com>, Jiri Pirko
<jiri@...nulli.us>, <pabeni@...hat.com>, John Fastabend
<john.fastabend@...il.com>, Alexander Lobakin <aleksander.lobakin@...el.com>,
Andrew Lunn <andrew@...n.ch>, Daniel Borkmann <daniel@...earbox.net>, "Edward
Cree" <ecree.xilinx@...il.com>, <netdev@...r.kernel.org>,
<bhelgaas@...gle.com>, <linux-pci@...r.kernel.org>, Alexander Duyck
<alexanderduyck@...com>, Willem de Bruijn <willemdebruijn.kernel@...il.com>
Subject: Re: [net-next PATCH 00/15] eth: fbnic: Add network driver for Meta
Platforms Host Network Interface
On 4/10/2024 12:58 PM, Jakub Kicinski wrote:
> On Wed, 10 Apr 2024 11:29:57 -0700 Florian Fainelli wrote:
>>> If we are going to be trying to come up with some special status maybe
>>> it makes sense to have some status in the MAINTAINERS file that would
>>> indicate that this driver is exclusive to some organization and not
>>> publicly available so any maintenance would have to be proprietary.
>>
>> I like that idea.
>
> +1, also first idea that came to mind but I was too afraid
> of bike shedding to mention it :) Fingers crossed? :)
>
+1, I think putting it in MAINTAINERS makes a lot of sense.
Powered by blists - more mailing lists