From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 0/3] clk: Fixup issues for clk_set_parent
Date: Mon, 08 Apr 2013 18:21:36 -0700 [thread overview]
Message-ID: <20130409012136.14359.33264@quantum> (raw)
In-Reply-To: <1364936979-20805-1-git-send-email-ulf.hansson@stericsson.com>
Quoting Ulf Hansson (2013-04-02 14:09:36)
> From: Ulf Hansson <ulf.hansson@linaro.org>
>
> These issues exist in the clk_set_parent API:
>
> * Race issue for spinlocks when updating the clock tree toplogy.
> * The feature of reparent to the orphan list is broken.
>
Taken into clk-next.
Thanks,
Mike
> This patchset fixes both problems. Patch 1 prepares for patch 2 and
> patch 3, which are where the real issues are resolved.
>
> Changes in v4:
> - Rebased on top Mike's clk reentrancy patches.
>
> Changes in v3:
> - Fix review comments from Mike.
> - Include fixup for allow reparent to the orphan list.
>
> Changes in v2:
> - Do not remove the existing __clk_reparent API.
> - Rebase patches.
>
> Ulf Hansson (3):
> clk: Restructure code for __clk_reparent
> clk: Fixup errorhandling for clk_set_parent
> clk: Fixup locking issues for clk_set_parent
>
> drivers/clk/clk.c | 193 ++++++++++++++++++++++++++++++++++++-----------------
> 1 file changed, 130 insertions(+), 63 deletions(-)
>
> --
> 1.7.10
prev parent reply other threads:[~2013-04-09 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 21:09 [PATCH V4 0/3] clk: Fixup issues for clk_set_parent Ulf Hansson
2013-04-02 21:09 ` [PATCH V4 1/3] clk: Restructure code for __clk_reparent Ulf Hansson
2013-04-02 21:09 ` [PATCH V4 2/3] clk: Fixup errorhandling for clk_set_parent Ulf Hansson
2013-04-02 21:09 ` [PATCH V4 3/3] clk: Fixup locking issues " Ulf Hansson
2013-04-04 10:35 ` Rajagopal Venkat
2013-04-04 19:28 ` Ulf Hansson
2013-04-15 5:56 ` Rajagopal Venkat
2013-04-09 1:21 ` Mike Turquette [this message]
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=20130409012136.14359.33264@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).