From: Wolfram Sang <wsa@the-dreams.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Stefan Wahren <stefan.wahren@i2se.com>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: [PATCH RFC] eeprom: at24: extend driver to plug into the NVMEM framework
Date: Thu, 20 Aug 2015 22:33:18 +0200 [thread overview]
Message-ID: <20150820203317.GB1635@katana> (raw)
In-Reply-To: <20150817152504.GI7537@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
> Wolfram Sang has been maintaining the AT24 driver since 2008. We need
> his ACK to this change, and since this is an i2c driver, he is also
> probably the path into mainline for this change.
Yes, currently I pick up at24 patches. I am open to move it to some
NVMEM framework in the future...
> But we should also look at the bigger picture. The AT25, MAX6875 and
> sunxi_sid drivers also have a binary file in /sys. It would be good to
> have some sort of plan what to do with these drivers, even if at the
> moment only AT24 is under discussion.
... but this surely has to be solved first.
Regards,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-20 20:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 2:54 Andrew Lunn
2015-08-16 8:28 ` Stefan Wahren
2015-08-16 13:11 ` Andrew Lunn
2015-08-16 15:37 ` Stefan Wahren
2015-08-17 13:01 ` Srinivas Kandagatla
2015-08-17 13:09 ` Andrew Lunn
2015-08-17 14:59 ` Srinivas Kandagatla
2015-08-17 15:25 ` Andrew Lunn
2015-08-17 15:41 ` Srinivas Kandagatla
2015-08-20 15:57 ` Maxime Ripard
2015-08-20 16:38 ` Andrew Lunn
2015-08-20 21:52 ` Maxime Ripard
2015-08-20 20:33 ` Wolfram Sang [this message]
2015-08-17 9:48 ` Srinivas Kandagatla
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=20150820203317.GB1635@katana \
--to=wsa@the-dreams.de \
--cc=andrew@lunn.ch \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stefan.wahren@i2se.com \
/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®