From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/3] clk: update users of "clk_register_mux" and "DEFINE_CLK_MUX"
Date: Wed, 21 Aug 2013 23:19:30 -0700 [thread overview]
Message-ID: <20130822061930.8231.89917@quantum> (raw)
In-Reply-To: <1375778065-21808-3-git-send-email-chander.kashyap@linaro.org>
Quoting Chander Kashyap (2013-08-06 01:34:24)
> As with the patch "clk-add-support-for-temporary-parent-clock-migration.patch"
> a new field "alternate_parent_name", is added to clk structure. This field can
> be passed using clk_register_mux API and DEFINE_CLK_MUX macro.
Nitpick: it's easier to search for the patch you mentioned if you quote
the actual patch $SUBJECT instead of the name of the patch file. In this
case, "clk: add support for temporary parent clock migration".
This invasive change is not necessary if the temporary parent stuff is
not added to the clock core and is instead left to the .set_parent
callbacks of custom clock providers.
Regards,
Mike
next prev parent reply other threads:[~2013-08-22 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 8:34 [RFC PATCH 0/3] add temporary parent migration support Chander Kashyap
2013-08-06 8:34 ` [RFC PATCH 1/3] clk: add support for temporary parent clock migration Chander Kashyap
2013-08-22 6:16 ` Mike Turquette
2013-08-22 7:53 ` Chander Kashyap
2013-08-06 8:34 ` [RFC PATCH 2/3] clk: update users of "clk_register_mux" and "DEFINE_CLK_MUX" Chander Kashyap
2013-08-22 6:19 ` Mike Turquette [this message]
2013-08-22 7:55 ` Chander Kashyap
2013-08-06 8:34 ` [RFC PATCH 3/3] clk: Exynos5250: Add alternate parent name for mout_cpu Chander Kashyap
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=20130822061930.8231.89917@quantum \
--to=mturquette@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).