linux-kernel - Re: [PATCH v3 0/3] new memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87zlf8f9u8.fsf@deeprootsystems.com>
Date:	Thu, 26 Mar 2009 10:54:55 -0700
From:	Kevin Hilman <khilman@...prootsystems.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, David Brownell <david-b@...bell.net>
Subject: Re: [PATCH v3 0/3] new memory_accessor interface and usage

Andrew Morton <akpm@...ux-foundation.org> writes:

> On Thu, 26 Mar 2009 10:22:10 -0700 Kevin Hilman <khilman@...prootsystems.com> wrote:
>
>> David Brownell <david-b@...bell.net> writes:
>> 
>> > 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.
>> 
>> Andrew,
>> 
>> What's the next step for this series?  It's one of those areas that
>> doesn't seem to have clear ownership so this seems to be falling
>> through the cracks.
>
> I've been mostly-awol for a couple of weeks, sorry.  It's presently
> stuck in my backlog queue along with everything else.  I'll start
> chewing on that queue next week.
>
> As the patch "is pretty much a blocking issue for merging more complete
> DaVinci platform support" I guess we'll be wanting it in 2.6.30, yes?

Yes, I'm strongly hoping for 2.6.30.

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/