From: "Don Bollinger" <don@thebollingers.org>
To: "'Jakub Kicinski'" <kuba@kernel.org>
Cc: "'Andrew Lunn'" <andrew@lunn.ch>, <arndb@arndb.de>,
<gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>,
<brandon_chuang@edge-core.com>, <wally_wang@accton.com>,
<aken_liu@edge-core.com>, <gulv@microsoft.com>,
<jolevequ@microsoft.com>, <xinxliu@microsoft.com>,
"'netdev'" <netdev@vger.kernel.org>,
"'Moshe Shemesh'" <moshe@nvidia.com>, <don@thebollingers.org>
Subject: RE: [PATCH v2] eeprom/optoe: driver to read/write SFP/QSFP/CMIS EEPROMS
Date: Fri, 5 Mar 2021 18:30:27 -0800 [thread overview]
Message-ID: <005e01d71230$ad203be0$0760b3a0$@thebollingers.org> (raw)
In-Reply-To: <20210305145518.57a765bc@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Fri, 5 Mar 2021 2:55 PM -0800 Jakub Kicinski wrote:
> 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.
These are not proprietary systems. The Network Operating Systems that use
optoe are open source projects, Linux based, available on github, and
contributing to the Linux source (see for example
https://github.com/Azure/SONiC). The switches that these NOSs run on are
open spec systems
(https://www.opencompute.org/wiki/Networking/SpecsAndDesigns). The fact
that they use the SDK from the switch silicon vendor should not mean they
are banished from the Linux community.
I am proposing acceptance of a commonly used implementation for accessing
SFPs because the one used by the netdev/netlink community does not fit the
architecture of the white box NOS/switch community. I am not trying to pick
sides, I am trying to make optoe available to both communities, to improve
EEPROM access for both of them.
Don
next prev parent reply other threads:[~2021-03-06 2:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210215193821.3345-1-don@thebollingers.org>
2021-02-26 22:34 ` [PATCH v2] eeprom/optoe: driver to read/write SFP/QSFP/CMIS EEPROMS Andrew Lunn
2021-02-27 2:46 ` Don Bollinger
2021-02-27 16:23 ` Andrew Lunn
2021-03-01 20:00 ` Don Bollinger
2021-03-01 20:45 ` Andrew Lunn
2021-03-05 19:07 ` Don Bollinger
2021-03-05 22:55 ` Jakub Kicinski
2021-03-06 2:30 ` Don Bollinger [this message]
2021-03-06 3:31 ` Andrew Lunn
2021-03-12 19:04 ` Don Bollinger
2021-03-12 19:59 ` Andrew Lunn
2021-03-13 21:35 ` Don Bollinger
2021-03-15 17:39 ` Jakub Kicinski
2021-03-15 18:09 ` Don Bollinger
2021-03-17 18:15 ` Andrew Lunn
2021-03-20 16:10 ` Pali Rohár
2021-03-26 18:43 ` Don Bollinger
2021-03-29 22:13 ` Pali Rohár
2021-03-23 20:32 ` Don Bollinger
2021-03-23 22:29 ` Andrew Lunn
2021-03-26 18:43 ` Don Bollinger
2021-03-26 19:46 ` Andrew Lunn
2021-03-26 20:16 ` Don Bollinger
2021-03-26 20:37 ` Andrew Lunn
2021-03-26 21:09 ` Don Bollinger
2021-03-26 21:54 ` Andrew Lunn
2021-03-26 22:30 ` Don Bollinger
2021-03-27 15:25 ` Andrew Lunn
2021-03-27 21:20 ` Don Bollinger
2021-03-27 12:40 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005e01d71230$ad203be0$0760b3a0$@thebollingers.org' \
--to=don@thebollingers.org \
--cc=aken_liu@edge-core.com \
--cc=andrew@lunn.ch \
--cc=arndb@arndb.de \
--cc=brandon_chuang@edge-core.com \
--cc=gregkh@linuxfoundation.org \
--cc=gulv@microsoft.com \
--cc=jolevequ@microsoft.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=wally_wang@accton.com \
--cc=xinxliu@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).