Skip to contentSkip to conversation

clk mux get_parent return type

DISCUSSION Rhyland Klein 2 participants 3 messages Feb 13, 2015 – Feb 15, 2015

lore
Share & tools
lore
#0 lore raw

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

Signature · 1 line
nvpublic
#1 lore raw
Quoted 4 lines · Rhyland Klein

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.

Quoted 8 lines

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.

Signature · 2 lines
Måns Rullgård
[email protected]
#2 lore raw
In reply to Rhyland Klein
Quoted 4 lines · Rhyland Klein

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.

Quoted 8 lines

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

The patch author is apparently no longer at TI (mail bounces). That might explain a thing or two.

Signature · 2 lines
Måns Rullgård
[email protected]