From: Stephen Boyd <sboyd@codeaurora.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: aggregate return codes of notify chains
Date: Fri, 7 Apr 2017 12:47:04 -0700 [thread overview]
Message-ID: <20170407194704.GG7065@codeaurora.org> (raw)
In-Reply-To: <1490091386-4014-1-git-send-email-pdeschrijver@nvidia.com>
On 03/21, Peter De Schrijver wrote:
> In case there are multiple notify chains for the same clocks (because they
> were registered by different users), we need to propagate potential failure
> of any single one of them to the caller. Otherwise we eg risk violating the
> V/f curve when a notifier is used for DVFS.
>
> Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> ---
Applied to clk-next. Let's see if anything blows up.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-04-07 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 10:16 [PATCH] clk: aggregate return codes of notify chains Peter De Schrijver
2017-04-07 19:47 ` Stephen Boyd [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=20170407194704.GG7065@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.