From: Rhyland Klein <rklein@nvidia.com>
To: Mike Turquette <mturquette@linaro.org>, Ambresh K <ambresh@ti.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: clk mux get_parent return type
Date: Fri, 13 Feb 2015 11:53:44 -0500 [thread overview]
Message-ID: <54DE2C18.2000708@nvidia.com> (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
--
nvpublic
next reply other threads:[~2015-02-13 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 16:53 Rhyland Klein [this message]
2015-02-15 12:10 ` clk mux get_parent return type Måns Rullgård
2015-02-15 12:15 ` Måns Rullgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DE2C18.2000708@nvidia.com \
--to=rklein@nvidia.com \
--cc=ambresh@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox