[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210305145518.57a765bc@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Fri, 5 Mar 2021 14:55:18 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: "Don Bollinger" <don@...bollingers.org>
Cc: "'Andrew Lunn'" <andrew@...n.ch>, <arndb@...db.de>,
<gregkh@...uxfoundation.org>, <linux-kernel@...r.kernel.org>,
<brandon_chuang@...e-core.com>, <wally_wang@...ton.com>,
<aken_liu@...e-core.com>, <gulv@...rosoft.com>,
<jolevequ@...rosoft.com>, <xinxliu@...rosoft.com>,
"'netdev'" <netdev@...r.kernel.org>,
"'Moshe Shemesh'" <moshe@...dia.com>
Subject: Re: [PATCH v2] eeprom/optoe: driver to read/write SFP/QSFP/CMIS
EEPROMS
On Fri, 5 Mar 2021 11:07:08 -0800 Don Bollinger wrote:
> Acknowledging your objections, I nonetheless request that optoe be accepted
> into upstream as an eeprom driver in drivers/misc/eeprom. It is a
> legitimate driver, with a legitimate user community, which deserves the
> benefits of being managed as a legitimate part of the linux kernel.
It's in the best interest of the community to standardize on how
we expect things to operate. You're free to do whatever you want
in your proprietary systems but please don't expect us to accept
a parallel, in now way superior method of accessing SFPs.
Powered by blists - more mailing lists