linux-kernel - Current state of regmap.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4E64D936.9030904@cam.ac.uk>
Date:	Mon, 05 Sep 2011 15:14:14 +0100
From:	Jonathan Cameron <jic23@....ac.uk>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Current state of regmap.

Hi Mark,

As my previous email said I've been messing around with regmap today.
I've run into a couple of bugs and was wondering if I'm running
behind the current version.  I've pulled what is up on kernel.org
for linux-next at the moment.

As I'm emailing anyway.  Everywhere other than regmap-debugfs max_register
is treated as the max valid.  In there we have a loop that is
for (i = 0; i < map->max_register; i++) so that treats it as one
larger than the max valid register index.

Thanks,

Jonathan.

p.s. Nice work by the way.
--
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/