From: Jisheng Zhang <jszhang@marvell.com>
To: <srinivas.pandruvada@linux.intel.com>, <lenb@kernel.org>,
<rjw@rjwysocki.net>, <viresh.kumar@linaro.org>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jisheng Zhang <jszhang@marvell.com>
Subject: [PATCH 0/3] cpufreq: intel_pstate: trivial improvements
Date: Mon, 27 Jun 2016 17:26:12 +0800 [thread overview]
Message-ID: <1467019575-664-1-git-send-email-jszhang@marvell.com> (raw)
The first patch fixes incorrect placement of __initdata
The second patch is to add __init/__initdata marker to some functions
or varaiables so that we can discard them.
The third patch declares pid_params/pstate_funcs/hwp_active as
__read_mostly, under the fact that they are mostly read and not
written to.
Jisheng Zhang (3):
intel_pstate: Fix incorrect placement of __initdata
intel_pstate: add __init/__initdata marker to some functions/variables
intel_pstate: Declare pid_params/pstate_funcs/hwp_active __read_mostly
drivers/cpufreq/intel_pstate.c | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
--
2.8.1
next reply other threads:[~2016-06-27 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 9:26 Jisheng Zhang [this message]
2016-06-27 9:26 ` [PATCH 1/3] intel_pstate: Fix incorrect placement of __initdata Jisheng Zhang
2016-06-27 9:26 ` [PATCH 2/3] intel_pstate: add __init/__initdata marker to some functions/variables Jisheng Zhang
2016-06-27 9:26 ` [PATCH 3/3] intel_pstate: Declare pid_params/pstate_funcs/hwp_active __read_mostly Jisheng Zhang
2016-06-27 9:43 ` [PATCH 0/3] cpufreq: intel_pstate: trivial improvements 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=1467019575-664-1-git-send-email-jszhang@marvell.com \
--to=jszhang@marvell.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®