From: "Andreas Färber" <afaerber@suse.de>
To: James Tai <james.tai@realtek.com>
Cc: "linux-realtek-soc@lists.infradead.org"
<linux-realtek-soc@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 00/14] ARM: dts: realtek: Introduce syscon
Date: Fri, 3 Jan 2020 03:58:50 +0100 [thread overview]
Message-ID: <f1f3fc5f-ae6c-b803-cb02-d06d60c442ce@suse.de> (raw)
In-Reply-To: <996a6968f411467cb987a14a0764726d@realtek.com>
Hi James,
Am 31.12.19 um 10:47 schrieb James Tai:
>> I'm waiting for your Acked-by of the blocks & numbers in these patches.
>> Other Realtek engineers are also invited to respond, of course.
>
> I have reviewed these patches.
Thanks - does anything need changes in patch 01 or is that ack'ed, too?
Regards,
Andreas
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer
HRB 36809 (AG Nürnberg)
next prev parent reply other threads:[~2020-01-03 2:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 18:21 [PATCH 00/14] ARM: dts: realtek: Introduce syscon Andreas Färber
2019-12-02 18:21 ` [PATCH 01/14] ARM: dts: rtd1195: Introduce iso and misc syscon Andreas Färber
2019-12-02 18:21 ` [PATCH 02/14] arm64: dts: realtek: rtd129x: Introduce CRT, " Andreas Färber
2019-12-30 14:40 ` James Tai
2019-12-02 18:21 ` [PATCH 03/14] arm64: dts: realtek: rtd139x: " Andreas Färber
2019-12-30 14:39 ` James Tai
2019-12-02 18:21 ` [PATCH 04/14] arm64: dts: realtek: rtd16xx: Introduce " Andreas Färber
2019-12-30 5:53 ` James Tai
2019-12-02 18:21 ` [PATCH 05/14] ARM: dts: rtd1195: Add CRT syscon node Andreas Färber
2019-12-31 9:16 ` James Tai
2019-12-02 18:21 ` [PATCH 06/14] dt-bindings: reset: Add Realtek RTD1195 Andreas Färber
2019-12-31 9:25 ` James Tai
2019-12-02 18:21 ` [PATCH 07/14] ARM: dts: rtd1195: Add reset nodes Andreas Färber
2019-12-31 9:27 ` James Tai
2019-12-02 18:21 ` [PATCH 08/14] ARM: dts: rtd1195: Add UART resets Andreas Färber
2019-12-31 9:28 ` James Tai
2019-12-02 18:21 ` [PATCH 09/14] arm64: dts: realtek: rtd16xx: Add CRT syscon node Andreas Färber
2019-12-30 14:43 ` James Tai
2019-12-02 18:22 ` [PATCH 10/14] ARM: dts: rtd1195: Add SB2 and SCPU Wrapper syscon nodes Andreas Färber
2019-12-31 9:30 ` James Tai
2019-12-02 18:22 ` [PATCH 11/14] arm64: dts: realtek: rtd129x: " Andreas Färber
2019-12-30 14:46 ` James Tai
2019-12-02 18:22 ` [PATCH 12/14] arm64: dts: realtek: rtd139x: " Andreas Färber
2019-12-30 14:45 ` James Tai
2019-12-02 18:22 ` [PATCH 13/14] arm64: dts: realtek: rtd16xx: " Andreas Färber
2019-12-30 14:45 ` James Tai
2019-12-02 18:22 ` [PATCH 14/14] dt-bindings: reset: rtd1295: Add SB2 reset Andreas Färber
2019-12-13 23:31 ` Rob Herring
2019-12-30 14:55 ` James Tai
2019-12-30 2:57 ` [PATCH 00/14] ARM: dts: realtek: Introduce syscon Andreas Färber
2019-12-31 9:47 ` James Tai
2020-01-03 2:58 ` Andreas Färber [this message]
2020-01-15 13:26 ` Andreas Färber
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=f1f3fc5f-ae6c-b803-cb02-d06d60c442ce@suse.de \
--to=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=james.tai@realtek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@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).