* clk mux get_parent return type
@ 2015-02-13 16:53 Rhyland Klein
2015-02-15 12:10 ` Måns Rullgård
2015-02-15 12:15 ` Måns Rullgård
0 siblings, 2 replies; 3+ messages in thread
From: Rhyland Klein @ 2015-02-13 16:53 UTC (permalink / raw)
To: Mike Turquette, Ambresh K; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: clk mux get_parent return type
2015-02-13 16:53 clk mux get_parent return type Rhyland Klein
@ 2015-02-15 12:10 ` Måns Rullgård
2015-02-15 12:15 ` Måns Rullgård
1 sibling, 0 replies; 3+ messages in thread
From: Måns Rullgård @ 2015-02-15 12:10 UTC (permalink / raw)
To: Rhyland Klein; +Cc: Mike Turquette, Ambresh K, linux-kernel
Rhyland Klein <rklein@nvidia.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@mansr.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: clk mux get_parent return type
2015-02-13 16:53 clk mux get_parent return type Rhyland Klein
2015-02-15 12:10 ` Måns Rullgård
@ 2015-02-15 12:15 ` Måns Rullgård
1 sibling, 0 replies; 3+ messages in thread
From: Måns Rullgård @ 2015-02-15 12:15 UTC (permalink / raw)
To: Rhyland Klein; +Cc: Mike Turquette, linux-kernel
Rhyland Klein <rklein@nvidia.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).
The patch author is apparently no longer at TI (mail bounces). That
might explain a thing or two.
--
Måns Rullgård
mans@mansr.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-02-15 12:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-13 16:53 clk mux get_parent return type Rhyland Klein
2015-02-15 12:10 ` Måns Rullgård
2015-02-15 12:15 ` Måns Rullgård
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox