From: Felix Brack <fb@ltec.ch>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
brgl@bgdev.pl
Subject: Re: nvmem: add driver for Microchip 24AA025E48 I2C eeprom / nodeID chip
Date: Wed, 24 Jan 2018 16:18:04 +0100 [thread overview]
Message-ID: <017877bf-5848-53c4-1f72-d630b3acaed4@ltec.ch> (raw)
In-Reply-To: <CAHp75VeEU1o=NVhtfuV=qK0t=UWrC+aCmq-HRQ5RZQm-Kwsf1g@mail.gmail.com>
On 24.01.2018 16:08, Andy Shevchenko 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
>
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
next prev parent reply other threads:[~2018-01-24 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 14:23 Felix Brack
2018-01-24 15:08 ` Andy Shevchenko
2018-01-24 15:10 ` Andy Shevchenko
2018-01-24 15:18 ` Felix Brack [this message]
2018-01-24 16:02 ` Bartosz Golaszewski
2018-01-25 14:37 ` Felix Brack
2018-01-25 21:46 ` Bartosz Golaszewski
2018-01-26 16:47 ` Felix Brack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=017877bf-5848-53c4-1f72-d630b3acaed4@ltec.ch \
--to=fb@ltec.ch \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®