From: Zhang Rui <rui.zhang@intel.com>
To: linux-pm@vger.kernel.org
Subject: [PATCH 0/5] thermal: convert ID allocation to IDA
Date: Wed, 21 Dec 2016 10:04:10 +0800 [thread overview]
Message-ID: <1482285855-2974-1-git-send-email-rui.zhang@intel.com> (raw)
Currently, thermal subsystem uses IDRs to allocate IDs, but actually
it only needs to know whether IDs are in use or not, and the ID to pointer
functionality of the IDR is unused.
That means it can use the more space-efficient IDA.
This patch set converts ID allocation to IDA for thermal subsystem.
PS: only build test is done for this patch set.
thanks,
rui
next reply other threads:[~2016-12-21 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 2:04 Zhang Rui [this message]
2016-12-21 2:04 ` [PATCH 1/5] thermal: core: convert ID allocation to IDA Zhang Rui
2016-12-21 2:04 ` [PATCH 2/5] thermal: share get_ida()/release_ida() for other thermal ida users Zhang Rui
2016-12-21 15:54 ` Matthew Wilcox
2016-12-21 2:04 ` [PATCH 3/5] thermal: cpu cooling: convert ID allocation to IDA Zhang Rui
2016-12-21 2:04 ` [PATCH 4/5] thermal: devfreq " Zhang Rui
2016-12-21 2:04 ` [PATCH 5/5] thermal: clock " Zhang Rui
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=1482285855-2974-1-git-send-email-rui.zhang@intel.com \
--to=rui.zhang@intel.com \
--cc=linux-pm@vger.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).