From: Doug Anderson <dianders@chromium.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"Tao Huang" <huangtao@rock-chips.com>,
平台组-汤云平 <typ@rock-chips.com>, "Lin Huang" <hl@rock-chips.com>,
"David Airlie" <airlied@linux.ie>,
"Michael Turquette" <mturquette@baylibre.com>,
"Derek Basehore" <dbasehore@chromium.org>,
"Stephen Boyd" <sboyd@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
myungjoo.ham@samsung.com, linux-clk <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
姚智情 <mark.yao@rock-chips.com>
Subject: Re: [RFC PATCH v1 2/6] clk: rockchip: rk3399: add SCLK_DDRCLK ID for ddrc
Date: Fri, 3 Jun 2016 06:25:24 -0700 [thread overview]
Message-ID: <CAD=FV=XuJ4mVtEh8qzQwcwO8UqqoX6+r6OTrWc9yUN93kbMe_w@mail.gmail.com> (raw)
In-Reply-To: <3d6d3147-00de-8ba4-a27a-a8f89854f4f7@rock-chips.com>
Hi,
On Fri, Jun 3, 2016 at 5:47 AM, Shawn Lin <shawn.lin@rock-chips.com> wrote:
> Ah, I missed the previous version as I think it should be from
> non-version to v2 rather than from non-version to v1, which IIRC is from
> Doug. :)
Yup, patch-numbering is 1-based, not 0-based, so typically you have
no-version => v2 => v3 => v99
-Doug
next prev parent reply other threads:[~2016-06-03 13:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 9:55 [RFC PATCH v1 0/6] rk3399 support ddr frequency scaling Lin Huang
2016-06-03 9:55 ` [RFC PATCH v1 1/6] rockchip: rockchip: add new clock-type for the ddrclk Lin Huang
2016-06-03 12:29 ` Shawn Lin
2016-06-06 2:24 ` hl
2016-06-03 12:51 ` Heiko Stübner
2016-06-06 3:20 ` hl
2016-06-06 3:20 ` hl
2016-06-03 9:55 ` [RFC PATCH v1 2/6] clk: rockchip: rk3399: add SCLK_DDRCLK ID for ddrc Lin Huang
2016-06-03 12:34 ` Shawn Lin
2016-06-03 12:36 ` Heiko Stübner
2016-06-03 12:47 ` Shawn Lin
2016-06-03 13:25 ` Doug Anderson [this message]
2016-06-03 9:55 ` [RFC PATCH v1 3/6] clk: rockchip: rk3399: add ddrc clock support Lin Huang
2016-06-03 12:56 ` Heiko Stübner
2016-06-06 3:25 ` hl
2016-06-03 9:55 ` [RFC PATCH v1 4/6] PM / devfreq: event: support rockchip dfi controller Lin Huang
2016-06-03 10:26 ` Chanwoo Choi
2016-06-06 3:50 ` hl
2016-06-03 16:54 ` Thierry Reding
2016-06-06 6:19 ` hl
2016-06-03 9:55 ` [RFC PATCH v1 5/6] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc Lin Huang
2016-06-03 9:55 ` [RFC PATCH v1 6/6] drm/rockchip: Add dmc notifier in vop driver Lin Huang
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='CAD=FV=XuJ4mVtEh8qzQwcwO8UqqoX6+r6OTrWc9yUN93kbMe_w@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=airlied@linux.ie \
--cc=dbasehore@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hl@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.com \
--cc=mturquette@baylibre.com \
--cc=myungjoo.ham@samsung.com \
--cc=sboyd@codeaurora.org \
--cc=shawn.lin@rock-chips.com \
--cc=typ@rock-chips.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).