From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/7] clk: gxbb: expose spifc clock
Date: Thu, 08 Sep 2016 11:12:19 -0700 [thread overview]
Message-ID: <m24m5qntvg.fsf@baylibre.com> (raw)
In-Reply-To: <20160907212754.GB12510@codeaurora.org> (Stephen Boyd's message of "Wed, 7 Sep 2016 14:27:54 -0700")
Stephen Boyd <sboyd@codeaurora•org> writes:
> On 09/07, Jerome Brunet wrote:
>> SPI clock is needed for the spifc driver, expose to DT
>> (and comment out in the clk driver)
>>
>> Signed-off-by: Jerome Brunet <jbrunet@baylibre•com>
>> ---
>
> Acked-by: Stephen Boyd <sboyd@codeaurora•org>
Applied,
Kevin
next prev parent reply other threads:[~2016-09-08 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 15:13 [PATCH 0/7] ARM: amlogic: Add spifc support to Amlogic's GXBB family Jerome Brunet
2016-09-07 15:13 ` [PATCH 1/7] pinctrl: amlogic: gxbb: add spifc pins Jerome Brunet
2016-09-08 18:08 ` Kevin Hilman
2016-09-07 15:13 ` [PATCH 2/7] pinctrl: amlogic: gxbb: add nand pins Jerome Brunet
2016-09-08 18:09 ` Kevin Hilman
2016-09-07 15:13 ` [PATCH 3/7] clk: gxbb: expose spifc clock Jerome Brunet
2016-09-07 21:27 ` Stephen Boyd
2016-09-08 18:12 ` Kevin Hilman [this message]
2016-09-07 15:13 ` [PATCH 4/7] spi: meson: Add GXBB compatible Jerome Brunet
2016-09-07 18:58 ` Mark Brown
2016-09-08 7:44 ` Neil Armstrong
2016-09-12 19:12 ` Applied "spi: meson: Add GXBB compatible" to the spi tree Mark Brown
2016-09-07 15:13 ` [PATCH 5/7] dt-bindings: spi-meson: Add GXBB Compatible string Jerome Brunet
2016-09-12 19:12 ` Applied "spi: meson: Add GXBB Compatible string" to the spi tree Mark Brown
2016-09-07 15:13 ` [PATCH 6/7] ARM64: dts: amlogic: add pins for spifc Jerome Brunet
2016-09-07 15:13 ` [PATCH 7/7] ARM64: dts: meson-gxbb: Add SPIFC node Jerome Brunet
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=m24m5qntvg.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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