[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YEL3ksdKIW7cVRh5@lunn.ch>
Date: Sat, 6 Mar 2021 04:31:30 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Don Bollinger <don@...bollingers.org>
Cc: 'Jakub Kicinski' <kuba@...nel.org>, 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
> 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
Powered by blists - more mailing lists