From: mark.yao@rock-chips•com (Mark yao)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v5 6/7] dt-bindings: display: rockchip: fill Documents for vop series
Date: Tue, 25 Jul 2017 08:30:59 +0800 [thread overview]
Message-ID: <59769143.2070508@rock-chips.com> (raw)
In-Reply-To: <20170724195300.uikqujxkioiomcyt@rob-hp-laptop>
On 2017?07?25? 03:53, Rob Herring wrote:
> On Thu, Jul 20, 2017 at 10:43:53AM +0800, Mark Yao wrote:
>> Signed-off-by: Mark Yao <mark.yao@rock-chips•com>
>> ---
>> Changes in v5:
>> - clean document commit title
>> - move changes description out of docummit commit msg
>>
>> Changes in v2:
>> - rename rk322x to rk3228
>> - correct some vop registers define
>>
>> Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt | 4 ++++
>> 1 file changed, 4 insertions(+)
> Acked-by: Rob Herring <robh@kernel•org>
>
>
>
Thanks for the Ack. :-)
--
?ark Yao
next prev parent reply other threads:[~2017-07-25 0:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 2:42 [PATCH v5 0/7] drm/rockchip: add all full framework vop support Mark Yao
2017-07-20 2:43 ` [PATCH v5 1/7] drm/rockchip: vop: initialize registers directly Mark Yao
2017-07-25 22:36 ` Heiko Stuebner
2017-07-26 0:59 ` Mark yao
2017-07-20 2:43 ` [PATCH v5 2/7] drm/rockchip: vop: move write_relaxed flags to vop register Mark Yao
2017-07-25 21:47 ` Heiko Stuebner
2017-07-26 6:17 ` Mark yao
2017-07-20 2:43 ` [PATCH v5 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers Mark Yao
2017-07-25 21:54 ` Heiko Stuebner
2017-07-26 6:17 ` Mark yao
2017-07-20 2:43 ` [PATCH v5 4/7] drm/rockchip: vop: group vop registers Mark Yao
2017-07-20 2:43 ` [PATCH v5 5/7] drm/rockchip: vop: add a series of vop support Mark Yao
2017-07-20 2:43 ` [PATCH v5 6/7] dt-bindings: display: rockchip: fill Documents for vop series Mark Yao
2017-07-24 19:53 ` Rob Herring
2017-07-25 0:30 ` Mark yao [this message]
2017-07-20 2:44 ` [PATCH v5 7/7] drm/rockchip: vop: rk3328: fix overlay abnormal Mark Yao
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=59769143.2070508@rock-chips.com \
--to=mark.yao@rock-chips$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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