LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] Misc devfreq_add_device() fixes
Date: Tue, 24 Apr 2018 15:35:15 -0700 [thread overview]
Message-ID: <20180424223521.28193-1-bjorn.andersson@linaro.org> (raw)
The first 5 patches corrects error handling, reoder things and stop holding the
devfreq mutex in devfreq_add_device(). The last patch validates that a client
doesn't attempt to provide a freq_table, as the implementation relies on the
freq_table being an internal representation of the associated device's opp
table.
Bjorn Andersson (6):
PM / devfreq: Free devfreq upon set_freq_table error
PM / devfreq: Use the device release function for cleanup
PM / devfreq: Reorder devfreq_add_device()
PM / devfreq: Remove unnecessary locking
PM / devfreq: Use put_device() on device_register error
PM / devfreq: Reject client provided freq_table
drivers/devfreq/devfreq.c | 73 ++++++++++++++++++++---------------------------
1 file changed, 31 insertions(+), 42 deletions(-)
--
2.16.2
next reply other threads:[~2018-04-24 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 22:35 Bjorn Andersson [this message]
2018-04-24 22:35 ` [PATCH 1/6] PM / devfreq: Free devfreq upon set_freq_table error Bjorn Andersson
2018-04-24 22:35 ` [PATCH 2/6] PM / devfreq: Use the device release function for cleanup Bjorn Andersson
2018-04-24 22:35 ` [PATCH 3/6] PM / devfreq: Reorder devfreq_add_device() Bjorn Andersson
2018-04-24 22:35 ` [PATCH 4/6] PM / devfreq: Remove unnecessary locking Bjorn Andersson
2018-04-24 22:35 ` [PATCH 5/6] PM / devfreq: Use put_device() on device_register error Bjorn Andersson
2018-04-24 22:35 ` [PATCH 6/6] PM / devfreq: Reject client provided freq_table Bjorn Andersson
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=20180424223521.28193-1-bjorn.andersson@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--subject='Re: [PATCH 0/6] Misc devfreq_add_device() fixes' \
/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
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).