From: Stephen Boyd <sboyd@codeaurora.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com
Subject: Re: [PATCH 1/4] clk: Enable compile testing for s2mps11 and max77686
Date: Tue, 1 Nov 2016 17:33:19 -0700 [thread overview]
Message-ID: <20161102003319.GK16026@codeaurora.org> (raw)
In-Reply-To: <1475441897-15730-2-git-send-email-krzk@kernel.org>
On 10/02, Krzysztof Kozlowski wrote:
> s2mps11 and max77686 clock drivers can be compile tested to increase
> build coverage.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.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:[~2016-11-02 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 20:58 [PATCH 0/4] clk/mfd/regulator/rtc: Enable compile testing for some Maxim/Samsung drivers Krzysztof Kozlowski
2016-10-02 20:58 ` [PATCH 1/4] clk: Enable compile testing for s2mps11 and max77686 Krzysztof Kozlowski
2016-11-02 0:33 ` Stephen Boyd [this message]
2016-10-02 20:58 ` [PATCH 2/4] regulator: Enable compile testing for Maxim and Samsung PMIC drivers Krzysztof Kozlowski
2016-10-04 2:40 ` Mark Brown
2016-10-04 9:30 ` Krzysztof Kozlowski
2016-10-02 20:58 ` [PATCH 3/4] rtc: Enable compile testing for Maxim and Samsung drivers Krzysztof Kozlowski
2016-11-04 23:12 ` Alexandre Belloni
2016-10-02 20:58 ` [PATCH 4/4] mfd: Enable compile testing for max77620 and max77686 Krzysztof Kozlowski
2016-10-26 12:19 ` Lee Jones
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=20161102003319.GK16026@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=broonie@kernel.org \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rtc-linux@googlegroups.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 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).