linux-kernel - Re: nvmem: add driver for Microchip 24AA025E48 I2C eeprom / nodeID chip

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]

Message-ID: <017877bf-5848-53c4-1f72-d630b3acaed4@ltec.ch>
Date:   Wed, 24 Jan 2018 16:18:04 +0100
From:   Felix Brack <fb@...c.ch>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        brgl@...ev.pl
Subject: Re: nvmem: add driver for Microchip 24AA025E48 I2C eeprom / nodeID
 chip


On 24.01.2018 16:08, Andy Shevchenko wrote:
> On Wed, Jan 24, 2018 at 4:23 PM, Felix Brack <fb@...c.ch> wrote:
>> Hello,
>>
>> About three years ago I wrote a driver for Microchip's 24AA025E48 I2C
>> eeprom/nodeID chip. At that time I placed the source files in
>> drivers/misc/eeprom. I never posted the code.
>> I now plan to rewrite the driver from scratch. Is it correct to place
>> the source code in drivers/nvmem and is there a special mailing list to
>> which the patch should be posted when ready?
>>
>> many thanks and kind regards, Felix
> 
> Does the existing driver [1] work for you (if you add ID there)?
> 
> [1]: at24
> 
Yes it does. Actually the driver I wrote 3 years ago is based on the
at24 driver. Lot's of code in my driver originates directly from the
at24 driver.

--
regards Felix