From: Curt Brune <curt@cumulusnetworks.com>
To: Laszlo Papp <lpapp@kde.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
patrickdepinguin@gmail.com, gregkh@linuxfoundation.org,
linux-i2c@vget.kernel.org
Subject: Re: [RFC] Creating an eeprom class
Date: Wed, 22 Jan 2014 09:18:12 -0800 [thread overview]
Message-ID: <20140122171812.GA29955@cumulusnetworks.com> (raw)
In-Reply-To: <CAOMwXhMvefuQJPZ_sbzySmvcyqkR+Lfh-11Gx3unGqyR2pREww@mail.gmail.com>
Hi Laszlo,
On Wed Jan 22 13:25, Laszlo Papp wrote:
>
> Was there any progress done? I saw the following thread, too, so
> including CC in the loop:
> http://www.spinics.net/lists/linux-i2c/msg13141.html
>
I have patches that adds a "eeprom_dev" class that I described in the
above thread. The patches also show how to register the at24 driver
with the EEPROM class.
We have been using the patch in production for almost a year now, with
good success.
I will send the patches to linux-i2c@vget.kernel.org shortly.
Cheers,
Curt
prev parent reply other threads:[~2014-01-22 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 13:25 [RFC] Creating an eeprom class Laszlo Papp
2014-01-22 17:18 ` Curt Brune [this message]
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=20140122171812.GA29955@cumulusnetworks.com \
--to=curt@cumulusnetworks.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@vget.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpapp@kde.org \
--cc=patrickdepinguin@gmail.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;
as well as URLs for NNTP newsgroup(s).