From: Stephen Boyd <sboyd@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] PM / OPP: compatible is an optional property
Date: Thu, 22 Sep 2016 12:24:30 -0700 [thread overview]
Message-ID: <483bea3c-a1b4-ce5d-e720-d69fc943ab50@codeaurora.org> (raw)
In-Reply-To: <be2c4fb0bb58f5b29facbc6f5aaf3dca13cf209e.1474450324.git.viresh.kumar@linaro.org>
On 09/21/2016 02:32 AM, Viresh Kumar wrote:
> It was never compulsory to have a compatible string in the OPP table.
> Fix the documentation to mark it optional.
>
> Also update its description a bit.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
Why? I'd prefer the compatible string to be required so we know what
sort of node it is.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-09-22 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 9:32 [PATCH 1/2] PM / OPP: compatible is an optional property Viresh Kumar
2016-09-21 9:32 ` [PATCH 2/2] PM / OPP: Multiple regulators aren't supported yet Viresh Kumar
[not found] ` <fc02fca412ffdb749bd811c8f1dc40fa2ae3fc3f.1474450324.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-09-23 19:59 ` Rob Herring
2016-09-26 5:07 ` Viresh Kumar
2016-09-22 19:24 ` Stephen Boyd [this message]
2016-09-23 5:15 ` [PATCH 1/2] PM / OPP: compatible is an optional property Viresh Kumar
2016-09-23 19:55 ` Rob Herring
2016-09-26 4:55 ` Viresh Kumar
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=483bea3c-a1b4-ce5d-e720-d69fc943ab50@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.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).