From: Heiko Stuebner <heiko@sntech.de>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
David Wu <david.wu@rock-chips.com>,
Caesar Wang <wxt@rock-chips.com>,
Elaine Zhang <zhangqing@rock-chips.com>,
Brian Norris <briannorris@chromium.org>,
linux-kernel@vger.kernel.org,
Shawn Lin <shawn.lin@rock-chips.com>,
Douglas Anderson <dianders@chromium.org>,
Will Deacon <will.deacon@arm.com>,
Jianqun Xu <jay.xu@rock-chips.com>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] arm64: dts: rk3399: add missing qos node
Date: Tue, 09 May 2017 23:40:11 +0200 [thread overview]
Message-ID: <3647345.gEejIkHfPK@phil> (raw)
In-Reply-To: <1491981044-24635-1-git-send-email-kever.yang@rock-chips.com>
Am Mittwoch, 12. April 2017, 15:10:41 CEST schrieb Kever Yang:
> Add qos setting reg for some peripheral like sd, usb, pcie.
>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
applied for 4.13
Thanks
Heiko
prev parent reply other threads:[~2017-05-09 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 7:10 [PATCH 1/4] arm64: dts: rk3399: add missing qos node Kever Yang
2017-04-12 7:10 ` [PATCH 2/4] arm64: dts: rk3399: add power domain for some peripheral Kever Yang
2017-05-09 21:40 ` Heiko Stuebner
2017-05-09 22:35 ` Heiko Stübner
2017-04-12 7:10 ` [PATCH 3/4] ARM: dts: rockchip: use pin constants to describe IO in pinctrl Kever Yang
2017-05-09 21:43 ` Heiko Stuebner
2017-05-10 1:25 ` Kever Yang
2017-05-10 13:55 ` Heiko Stuebner
2017-04-12 7:10 ` [PATCH 4/4] arm64: dts: rk3399: add pinctrl for some peripheral Kever Yang
2017-05-09 21:43 ` Heiko Stuebner
2017-05-09 21:40 ` Heiko Stuebner [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=3647345.gEejIkHfPK@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=jay.xu@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=wxt@rock-chips.com \
--cc=zhangqing@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