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: <CAHp75VcD0g2g-HBJV2zBH3CDLop62U49sekByGvcKwJwV73owA@mail.gmail.com>
Date:   Wed, 24 Jan 2018 17:10:24 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Felix Brack <fb@...c.ch>, Bartosz Golaszewski <brgl@...ev.pl>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: nvmem: add driver for Microchip 24AA025E48 I2C eeprom / nodeID chip

+Bartosh

On Wed, Jan 24, 2018 at 5:08 PM, Andy Shevchenko
<andy.shevchenko@...il.com> 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
>
> --
> With Best Regards,
> Andy Shevchenko



-- 
With Best Regards,
Andy Shevchenko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ