From: Stephen Boyd <sboyd@codeaurora.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip clk fixes for 4.7
Date: Mon, 20 Jun 2016 17:02:40 -0700 [thread overview]
Message-ID: <20160621000240.GD1521@codeaurora.org> (raw)
In-Reply-To: <6554609.UWKLgmyVYi@diego>
On 06/08, Heiko Stübner wrote:
> Hi Mike, Stephen,
>
> please find below some accumulated small-scale fixes that would be nice to have
> in 4.7. So if nothing stands out, please pull
>
>
Pulled into clk-fixes.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] Rockchip clk fixes for 4.7
Date: Mon, 20 Jun 2016 17:02:40 -0700 [thread overview]
Message-ID: <20160621000240.GD1521@codeaurora.org> (raw)
In-Reply-To: <6554609.UWKLgmyVYi@diego>
On 06/08, Heiko Stübner wrote:
> Hi Mike, Stephen,
>
> please find below some accumulated small-scale fixes that would be nice to have
> in 4.7. So if nothing stands out, please pull
>
>
Pulled into clk-fixes.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-06-21 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 17:37 [GIT PULL] Rockchip clk fixes for 4.7 Heiko Stübner
2016-06-21 0:02 ` Stephen Boyd [this message]
2016-06-21 0:02 ` 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=20160621000240.GD1521@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 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.