From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] PM / OPP: rename functions to dev_pm_opp*
Date: Fri, 20 Sep 2013 07:38:08 -0500 [thread overview]
Message-ID: <20130920123808.GA22176@kahuna> (raw)
In-Reply-To: <CAKohpoku7n6b2dDKD=+3DqG4pHtmWoeXZnAt3EoFRp+rNFofYA@mail.gmail.com>
On 12:44-20130920, Viresh Kumar wrote:
> On 20 September 2013 02:33, Nishanth Menon <nm@ti.com> wrote:
> > opp_get_opp_count
> > opp_find_freq_exact
> > opp_init_cpufreq_table
> > opp_free_cpufreq_table
>
> The only problem I see is that routines names for few of them are getting
> really long now.. Otherwise not much I could find...
I am open to suggestions if any one feels we can improve this better.
>
> Though you had following changes, which you could have avoided in this
> hard to review patchset:
>
> diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
> new_opp = [-kzalloc(sizeof(struct
> opp),-]{+kzalloc(sizeof(*new_opp),+} GFP_KERNEL);
> new_opp = [-kmalloc(sizeof(struct
> opp),-]{+kmalloc(sizeof(*new_opp),+} GFP_KERNEL);
>
> It is almost impossible to catch these with naked eyes for such long
> patches.. I took help of --word-diff though :)
I believe that change was from Patch #2[1]
yes, you are right, I had squashed this patch in to squelch checkpatch
warnings:
CHECK: Prefer kzalloc(sizeof(*new_opp)...) over kzalloc(sizeof(struct
dev_pm_opp)...)
#177: FILE: drivers/base/power/opp.c:406:
+ new_opp = kzalloc(sizeof(struct dev_pm_opp), GFP_KERNEL);
CHECK: Prefer kmalloc(sizeof(*new_opp)...) over kmalloc(sizeof(struct
dev_pm_opp)...)
#191: FILE: drivers/base/power/opp.c:495:
+ new_opp = kmalloc(sizeof(struct dev_pm_opp), GFP_KERNEL);
I had added a comment:
" Minor checkpatch warning fixes as a result of this change was fixed as
well."
Would you suggest I split the change off to a separate patch or improve
the comment a little more?
>
> If no one else sees these as problems then feel free to add my:
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
[1] https://patchwork.kernel.org/patch/2913551/
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-09-20 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 21:03 [PATCH 0/3] PM / OPP: rename to dev_pm_opp * equivalents Nishanth Menon
2013-09-19 21:03 ` [PATCH 1/3] PM / OPP: rename functions to dev_pm_opp* Nishanth Menon
2013-09-20 7:14 ` Viresh Kumar
2013-09-20 12:38 ` Nishanth Menon [this message]
2013-09-20 16:51 ` Viresh Kumar
2013-09-20 19:07 ` Nishanth Menon
2013-09-19 21:03 ` [PATCH 2/3] PM / OPP: rename data structures to dev_pm equivalents Nishanth Menon
2013-09-19 21:03 ` [PATCH 3/3] PM / OPP: rename header to linux/pm_opp.h Nishanth Menon
2013-09-19 21:14 ` [PATCH 0/3] PM / OPP: rename to dev_pm_opp * equivalents Nishanth Menon
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=20130920123808.GA22176@kahuna \
--to=nm@ti.com \
--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).