From: Andrew Lunn <andrew@lunn.ch>
To: Don Bollinger <don@thebollingers.org>
Cc: 'Jakub Kicinski' <kuba@kernel.org>,
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>
Subject: Re: [PATCH v2] eeprom/optoe: driver to read/write SFP/QSFP/CMIS EEPROMS
Date: Sat, 6 Mar 2021 04:31:30 +0100 [thread overview]
Message-ID: <YEL3ksdKIW7cVRh5@lunn.ch> (raw)
In-Reply-To: <005e01d71230$ad203be0$0760b3a0$@thebollingers.org>
> 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.
Please could you expand on this. I've given suggests as to how the new
netlink KAPI could be used for this use case, without being attached
to a netdev. And you have said nothing about why it cannot be made to
work. You cannot argue the architecture does not fit without actually
saying why it does not fit.
Andrew
next prev parent reply other threads:[~2021-03-06 3:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 19:38 [PATCH v2] eeprom/optoe: driver to read/write SFP/QSFP/CMIS EEPROMS Don Bollinger
2021-02-26 22:34 ` 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
2021-03-06 3:31 ` Andrew Lunn [this message]
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
2021-03-23 14:12 ` Greg KH
2021-03-23 18:43 ` Don Bollinger
2021-03-23 18:59 ` 'Greg KH'
2021-03-23 19:08 ` Don Bollinger
2021-03-23 19:12 ` '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=YEL3ksdKIW7cVRh5@lunn.ch \
--to=andrew@lunn.ch \
--cc=aken_liu@edge-core.com \
--cc=arndb@arndb.de \
--cc=brandon_chuang@edge-core.com \
--cc=don@thebollingers.org \
--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