From: David Brownell <david-b@pacbell.net>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] new memory_accessor interface and usage
Date: Mon, 16 Mar 2009 16:10:06 -0700 [thread overview]
Message-ID: <200903161610.06469.david-b@pacbell.net> (raw)
In-Reply-To: <1237239379-24186-1-git-send-email-khilman@deeprootsystems.com>
On Monday 16 March 2009, Kevin Hilman wrote:
> This series adds an interface by which other kernel code can read/write
> persistent memory such as I2C or SPI EEPROMs, or devices which provide
> NVRAM. Use cases include storage of board-specific configuration data
> like Ethernet addresses and sensor calibrations, etc.
Looks OK to me. Once this goes in (with support for I2C and SPI EEPROMs)
then various RTC's NVRAM support can be updated too ... at a quick count,
that makes nine more drivers that can easily support this.
I kind of like letting Linux have the option of using this kind of
persistent storage, instead of keeping it so that only bootloaders
(and maybe some userspace code) ever touch it.
- Dave
next prev parent reply other threads:[~2009-03-16 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 21:36 [PATCH v3 0/3] new memory_accessor interface and usage Kevin Hilman
2009-03-16 21:36 ` [PATCH v3 1/3] memory_accessor: new interface for reading/writing persistent memory Kevin Hilman
2009-03-16 21:36 ` [PATCH v3 2/3] Implement the new memory_accessor interface for I2C EEPROM Kevin Hilman
2009-03-16 21:36 ` [PATCH v3 3/3] Implement the new memory_accessor interfaces for SPI EEPROMs: Kevin Hilman
2009-03-16 23:10 ` David Brownell [this message]
2009-03-26 17:22 ` [PATCH v3 0/3] new memory_accessor interface and usage Kevin Hilman
2009-03-26 17:51 ` Andrew Morton
2009-03-26 17:54 ` Kevin Hilman
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=200903161610.06469.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.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