Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <CAHp75VeEU1o=NVhtfuV=qK0t=UWrC+aCmq-HRQ5RZQm-Kwsf1g@mail.gmail.com>
References: <f6309da6-48b7-25c9-2a0e-969cac171fc6@ltec.ch> <CAHp75VeEU1o=NVhtfuV=qK0t=UWrC+aCmq-HRQ5RZQm-Kwsf1g@mail.gmail.com>
From:   Andy Shevchenko <andy.shevchenko@gmail.com>
Date:   Wed, 24 Jan 2018 17:10:24 +0200
Message-ID: <CAHp75VcD0g2g-HBJV2zBH3CDLop62U49sekByGvcKwJwV73owA@mail.gmail.com>
Subject: Re: nvmem: add driver for Microchip 24AA025E48 I2C eeprom / nodeID chip
To:     Felix Brack <fb@ltec.ch>, Bartosz Golaszewski <brgl@bgdev.pl>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

+Bartosh

On Wed, Jan 24, 2018 at 5:08 PM, Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
> On Wed, Jan 24, 2018 at 4:23 PM, Felix Brack <fb@ltec.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