linux-kernel - clk mux get_parent return type

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-next>] [day] [month] [year] [list]

Message-ID: <54DE2C18.2000708@nvidia.com>
Date:	Fri, 13 Feb 2015 11:53:44 -0500
From:	Rhyland Klein <rklein@...dia.com>
To:	Mike Turquette <mturquette@...aro.org>, Ambresh K <ambresh@...com>
CC:	<linux-kernel@...r.kernel.org>
Subject: clk mux get_parent return type

I saw a series of patches posted last year by Ambresh which addresses
(at least mostly) changing the return type of clk_mux_get_parent.
Namely, this series changing it to an int from an u8.

http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/179367.html

I am running into this error right now, and noticed that linux-next
still seems to use u8's, as this series seems to have been dropped. I
didn't see anything that suggested that this was on purpose, but I
wanted to find out if there was a reason this was dropped or if it just
got forgotten about (I haven't found a V3 which should have addressed
fixing all the get_parent return values yet).

-rhyland

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