linux-kernel - Re: clk mux get

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

Message-ID: <yw1xvbj38jet.fsf@unicorn.mansr.com>
Date:	Sun, 15 Feb 2015 12:10:34 +0000
From:	Måns Rullgård <mans@...sr.com>
To:	Rhyland Klein <rklein@...dia.com>
Cc:	Mike Turquette <mturquette@...aro.org>, Ambresh K <ambresh@...com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: clk mux get_parent return type

Rhyland Klein <rklein@...dia.com> writes:

> 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).

I ran into this error myself just now, and it's quite annoying.  It
would be great if it got fixed.

-- 
Måns Rullgård
mans@...sr.com
--
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/