From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= <mans@mansr.com>
To: Rhyland Klein <rklein@nvidia.com>
Cc: Mike Turquette <mturquette@linaro.org>, Ambresh K <ambresh@ti.com>,
        <linux-kernel@vger.kernel.org>
Subject: Re: clk mux get_parent return type
References: <54DE2C18.2000708@nvidia.com>
Date: Sun, 15 Feb 2015 12:10:34 +0000
In-Reply-To: <54DE2C18.2000708@nvidia.com> (Rhyland Klein's message of "Fri,
	13 Feb 2015 11:53:44 -0500")
Message-ID: <yw1xvbj38jet.fsf@unicorn.mansr.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1106
Lines: 26

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/