From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: Add doc for Firefly ROC-RK3308-CC board
Date: Thu, 31 Oct 2019 16:36:37 +0100 [thread overview]
Message-ID: <314513738.FDhnDVbnjr@phil> (raw)
In-Reply-To: <20191030072648.29738-1-andy.yan@rock-chips.com>
Am Mittwoch, 30. Oktober 2019, 08:26:48 CET schrieb Andy Yan:
> Add compatible for Firefly ROC-RK3308-CC board.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
applied both patches for 5.5, with some small fixes.
Thanks
Heiko
prev parent reply other threads:[~2019-10-31 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 7:26 [PATCH 1/2] dt-bindings: Add doc for Firefly ROC-RK3308-CC board Andy Yan
2019-10-30 7:28 ` [PATCH 2/2] arm64: dts: rockchip: Add devicetree for board roc-rk3308-cc Andy Yan
2019-10-31 15:36 ` 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=314513738.FDhnDVbnjr@phil \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
/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).