From: Stephen Boyd <sboyd@codeaurora.org>
To: Michael Turquette <mturquette@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/5] blackfin: Use generic clkdev.h header
Date: Wed, 10 Jan 2018 13:20:17 -0800 [thread overview]
Message-ID: <20180110212017.GO21040@codeaurora.org> (raw)
In-Reply-To: <20180103013516.18844-2-sboyd@codeaurora.org>
On 01/02, Stephen Boyd wrote:
> The generic header file is equivalent to the blackfin version, so
> just use the generic one.
>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2018-01-10 21:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 1:35 [PATCH 0/5] Remove asm/clkdev.h and privatize __clk{get,put}() Stephen Boyd
2018-01-03 1:35 ` [PATCH 1/5] blackfin: Use generic clkdev.h header Stephen Boyd
2018-01-10 21:20 ` Stephen Boyd [this message]
2018-01-03 1:35 ` [PATCH 2/5] clk: Prepare to remove asm-generic/clkdev.h Stephen Boyd
2018-01-10 21:20 ` Stephen Boyd
2018-01-03 1:35 ` [PATCH 3/5] arch: Remove clkdev.h asm-generic from Kbuild Stephen Boyd
2018-01-03 8:43 ` Geert Uytterhoeven
2018-01-03 8:43 ` Geert Uytterhoeven
2018-01-03 15:37 ` Arnd Bergmann
2018-01-10 21:20 ` Stephen Boyd
2018-01-03 1:35 ` [PATCH 4/5] clk: sunxi: Use CLK_IS_CRITICAL flag for critical clks Stephen Boyd
2018-01-03 2:58 ` Chen-Yu Tsai
2018-01-03 17:01 ` Stephen Boyd
2018-01-04 13:13 ` Maxime Ripard
2018-01-10 21:20 ` Stephen Boyd
2018-01-03 1:35 ` [PATCH 5/5] clk: Move __clk_{get,put}() into private clk.h API Stephen Boyd
2018-01-10 21:20 ` Stephen Boyd
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=20180110212017.GO21040@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.