linux-kernel - Re: [PATCH] regmap: fix return value in regcache-indexed read call.

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: <4EF20C40.3060909@criticallink.com>
Date:	Wed, 21 Dec 2011 11:41:36 -0500
From:	Michael Williamson <michael.williamson@...ticallink.com>
To:	Michael Williamson <michael.williamson@...ticallink.com>
CC:	linux-kernel@...r.kernel.org, broonie@...nsource.wolfsonmicro.com,
	gregkh@...e.de
Subject: Re: [PATCH] regmap: fix return value in regcache-indexed read call.

On 12/21/2011 10:48 AM, Michael Williamson wrote:
> The regcache_read() API for regmap requires a 0 return value for
> successful cached reads.  The read method for the indexed type
> cache implementation is returning the positive map offset for a
> successful read, which is incorrect.  Fix it.
>
[...]

Looks like this cache type is due to be removed in linux-next.  Please
withdraw.  Thanks.

http://permalink.gmane.org/gmane.linux.kernel/1217338

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