From: Stephen Boyd <sboyd@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] PM / OPP: Rename structures for clarity
Date: Thu, 18 Feb 2016 14:08:41 -0800 [thread overview]
Message-ID: <20160218220841.GM4847@codeaurora.org> (raw)
In-Reply-To: <e9363b2c42e7082b442c81d96d572c4323559cf0.1455612454.git.viresh.kumar@linaro.org>
On 02/16, Viresh Kumar wrote:
> Stephen pointed out recently, that few structures always confuse him as
> they aren't named properly. And this patch tries to address that:
>
> Names are updated as:
> - device_opp or dev_opp -> opp_table
> - dev_opp_list -> opp_tables
> - dev_opp_list_lock -> opp_table_lock
> - device_list_opp -> opp_device (it was never a list, but a structure)
> - list_dev -> opp_dev
> - And similar changes in comments and function names as well.
>
> This also fixes checkpatch warnings that were generated with this patch.
>
> No functional changes.
>
> Suggested-by: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-02-18 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 8:47 [PATCH 1/2] PM / OPP: Fix incorrect comments Viresh Kumar
2016-02-16 8:47 ` [PATCH 2/2] PM / OPP: Rename structures for clarity Viresh Kumar
2016-02-18 22:08 ` Stephen Boyd [this message]
2016-02-18 19:52 ` [PATCH 1/2] PM / OPP: Fix incorrect comments Rafael J. Wysocki
2016-02-18 22:08 ` Stephen Boyd
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=20160218220841.GM4847@codeaurora.org \
--to=sboyd@codeaurora.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=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 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.