From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] fixes for struct clk_core migration
Date: Mon, 8 Sep 2014 23:07:46 -0700 [thread overview]
Message-ID: <1410242868-14750-1-git-send-email-mturquette@linaro.org> (raw)
A few build issues have popped up with more extensive testing of the
patches to split the clock framework into a proper provider/consumer
relationship. [0]
The first patch adapts Intel's LPSS driver to use the clock provider
APIs. If no one objects to this patch then I will fold it into Tomeu's
patch #2. [1]
Tomeu, can you run your Coccinelle script again against all of arch/ and
drivers/ to make sure nothing else was left out?
The second patch brings the asm-generic version of clkdev.h up to speed
with all of the asm-specific versions, by not declaring __clk_get and
__clk_put if CONFIG_COMMON_CLK is set. If no one objects to this patch
then I will move it to the front of the patch stack when rebasing
Tomeu's series.
[0] http://lkml.kernel.org/r/<1409758148-20104-1-git-send-email-tomeu.vizoso@collabora.com>
[1] http://lkml.kernel.org/r/<1409758317-20564-1-git-send-email-tomeu.vizoso@collabora.com>
Mike Turquette (2):
acpi: lpss: convert from struct clk to struct clk_core
asm-generic: COMMON_CLK defines __clk_{get,put}
drivers/acpi/acpi_lpss.c | 6 +++---
include/asm-generic/clkdev.h | 2 ++
include/linux/platform_data/clk-lpss.h | 2 +-
3 files changed, 6 insertions(+), 4 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-09-09 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 6:07 Mike Turquette [this message]
2014-09-09 6:07 ` [PATCH 1/2] acpi: lpss: convert from struct clk to struct clk_core Mike Turquette
2014-09-09 13:16 ` Rafael J. Wysocki
2014-09-09 13:52 ` Mika Westerberg
2014-09-10 5:30 ` Heikki Krogerus
2014-09-09 6:11 ` [PATCH 2/2] asm-generic: COMMON_CLK defines __clk_{get,put} Mike Turquette
2014-09-09 15:21 ` [PATCH 0/2] fixes for struct clk_core migration Tomeu Vizoso
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=1410242868-14750-1-git-send-email-mturquette@linaro.org \
--to=mturquette@linaro.org \
--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).