From: Stephen Boyd <sboyd@codeaurora.org>
To: Romain Perier <romain.perier@gmail.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Heiko Stübner" <heiko@sntech.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188
Date: Wed, 9 Sep 2015 14:47:05 -0700 [thread overview]
Message-ID: <20150909214705.GV15099@codeaurora.org> (raw)
In-Reply-To: <CABgxDoJRdF_k0EZLrEWXqpDrmj5LVRL24izGLJY4AmtUNOk7PQ@mail.gmail.com>
On 09/09, Romain Perier wrote:
> so, which of you does take the patch for -rc1 ?
>
Please stop top posting. I was going to take it after -rc1 is
tagged, but I can't tell what branch this is based on. It doesn't
apply to clk-next, nor to torvalds' tree, or linux-next. Is there
some other patch out there that's also needed?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Romain Perier <romain.perier@gmail.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-clk@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Michael Turquette" <mturquette@baylibre.com>
Subject: Re: [PATCH v2] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188
Date: Wed, 9 Sep 2015 14:47:05 -0700 [thread overview]
Message-ID: <20150909214705.GV15099@codeaurora.org> (raw)
In-Reply-To: <CABgxDoJRdF_k0EZLrEWXqpDrmj5LVRL24izGLJY4AmtUNOk7PQ@mail.gmail.com>
On 09/09, Romain Perier wrote:
> so, which of you does take the patch for -rc1 ?
>
Please stop top posting. I was going to take it after -rc1 is
tagged, but I can't tell what branch this is based on. It doesn't
apply to clk-next, nor to torvalds' tree, or linux-next. Is there
some other patch out there that's also needed?
--
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: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188
Date: Wed, 9 Sep 2015 14:47:05 -0700 [thread overview]
Message-ID: <20150909214705.GV15099@codeaurora.org> (raw)
In-Reply-To: <CABgxDoJRdF_k0EZLrEWXqpDrmj5LVRL24izGLJY4AmtUNOk7PQ@mail.gmail.com>
On 09/09, Romain Perier wrote:
> so, which of you does take the patch for -rc1 ?
>
Please stop top posting. I was going to take it after -rc1 is
tagged, but I can't tell what branch this is based on. It doesn't
apply to clk-next, nor to torvalds' tree, or linux-next. Is there
some other patch out there that's also needed?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-09-09 21:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 9:32 [PATCH v2] clk: rockchip: Add pclk_peri to critical clocks on RK3066/RK3188 Romain Perier
2015-08-23 9:32 ` Romain Perier
2015-08-23 9:32 ` Romain Perier
2015-08-31 14:42 ` Romain Perier
2015-08-31 14:42 ` Romain Perier
2015-09-04 6:50 ` Romain Perier
2015-09-04 6:50 ` Romain Perier
2015-09-04 6:50 ` Romain Perier
2015-09-04 16:24 ` Stephen Boyd
2015-09-04 16:24 ` Stephen Boyd
2015-09-04 16:24 ` Stephen Boyd
2015-09-05 16:12 ` Romain Perier
2015-09-05 16:12 ` Romain Perier
2015-09-09 17:58 ` Romain Perier
2015-09-09 17:58 ` Romain Perier
2015-09-09 21:47 ` Stephen Boyd [this message]
2015-09-09 21:47 ` Stephen Boyd
2015-09-09 21:47 ` Stephen Boyd
2015-09-10 7:05 ` Romain Perier
2015-09-10 7:05 ` Romain Perier
2015-09-10 16:40 ` Michael Niewoehner
2015-09-10 16:40 ` Michael Niewoehner
2015-09-10 16:40 ` Michael Niewoehner
2015-09-10 20:51 ` Stephen Boyd
2015-09-10 20:51 ` 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=20150909214705.GV15099@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=romain.perier@gmail.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.