lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 11 Jun 2018 11:31:01 -0700
From:   Don Bollinger <don@...bollingers.org>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, brandon_chuang@...e-core.com,
        wally_wang@...ton.com, roy_lee@...e-core.com,
        rick_burchett@...e-core.com, quentin.chang@...ntatw.com,
        steven.noble@...switch.com, jeffrey.townsend@...switch.com,
        scotte@...ulusnetworks.com, roopa@...ulusnetworks.com,
        David Ahern <dsa@...ulusnetworks.com>,
        luke.williams@...onical.com, Guohan Lu <gulv@...rosoft.com>,
        Xin Liu <xinxliu@...rosoft.com>, steve.joiner@...isar.com
Subject: Re: [PATCH] optoe: driver to read/write SFP/QSFP EEPROMs

On Sun, Jun 10, 2018 at 09:56:00PM -0700, Randy Dunlap wrote:
> Hi,
> 
> On 06/10/2018 09:25 PM, Don Bollinger wrote:
> > diff --git a/drivers/misc/eeprom/Kconfig b/drivers/misc/eeprom/Kconfig
> > index 68a1ac929917..9a08e12756ee 100644
> > --- a/drivers/misc/eeprom/Kconfig
> > +++ b/drivers/misc/eeprom/Kconfig
> > @@ -111,4 +111,22 @@ config EEPROM_IDT_89HPESX
> >  	  This driver can also be built as a module. If so, the module
> >  	  will be called idt_89hpesx.
> >  
> > +config EEPROM_OPTOE
> > +	tristate "read/write access to SFP* & QSFP* EEPROMs"
> > +	depends on I2C && SYSFS
> > +	help
> > +	  If you say yes here you get support for read and write access to
> > +	  the EEPROM of SFP and QSFP type optical and copper transceivers.
> > +	  Includes all devices which conform to the sff-8436 and sff-8472
> 
> 	  This includes
> and then please s/sff/SFF/ (2 places).

Got it.  I'll make the changes in the next version.

Don

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ