From: Stephen Boyd <sboyd@codeaurora.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip clock updates for 4.15 round 1
Date: Wed, 1 Nov 2017 22:36:29 -0700 [thread overview]
Message-ID: <20171102053629.GO30645@codeaurora.org> (raw)
In-Reply-To: <14384670.j3hM3TuojQ@phil>
On 10/17, Heiko Stuebner wrote:
> Hi Mike, Stephen,
j
> please find below the (tiny) first round of Rockchip clock changes for 4.15.
> Right now there isn't any more in the pipeline, but who knows that may
> change yet.
Thanks. Pulled.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-11-02 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 17:43 [GIT PULL] Rockchip clock updates for 4.15 round 1 Heiko Stuebner
2017-10-26 7:18 ` Heiko Stuebner
2017-11-02 5:36 ` Stephen Boyd [this message]
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=20171102053629.GO30645@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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 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).