linux-kernel - Re: [PATCH 2/8] regmap: Add the indexed cache support

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: <50057593.3050808@metafoo.de>
Date:	Tue, 17 Jul 2012 16:24:19 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...com>,
	Graeme Gregory <gg@...mlogic.co.uk>,
	Samuel Oritz <sameo@...ux.intel.com>
Subject: Re: [PATCH 2/8] regmap: Add the indexed cache support

On 07/17/2012 01:16 PM, Mark Brown wrote:
> On Fri, Sep 02, 2011 at 10:16:06PM +0200, Lars-Peter Clausen wrote:
> 
>> I have some patches for the rbtree register cache code, which reduce some of
>> it's complexity and also implements the adjacent node merging and allows
>> smaller holes in the rbnodes register block if the block is smaller then an
>> rbnode. Currently these patches are based on the ASoC register cache code, but
>> they should be easy to rework onto of the regmap register cache code.
> 
> Dimitris just reminded me about what you said here - do you still have
> those patches floating around?  This would really useful and would
> make some other optimistations like not cacheing default values much
> easier.

Yes, I still have it, but it's on a machine which is currently broken and I
wont get the replacement part until next week.

- Lars
--
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/