From: "Andreas Färber" <afaerber@suse.de>
To: Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, "Roc He" <hepeng@zidoo.tv>,
蒋丽琴 <jiang.liqin@geniatech.com>
Subject: Re: [PATCH v2 2/3] watchdog: Add Realtek RTD1295
Date: Sun, 10 Sep 2017 18:24:51 +0200 [thread overview]
Message-ID: <155916fd-1689-9a59-3e7c-9e9768a98057@suse.de> (raw)
In-Reply-To: <89c4a85d-fbc7-6fcf-6ff4-63c5580837f8@roeck-us.net>
Am 10.09.2017 um 17:17 schrieb Guenter Roeck:
> On 09/04/2017 04:16 PM, Andreas Färber wrote:
>> Add a watchdog driver for the Realtek RTD1295 SoC.
>>
>> Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_watchdog.c code and
>> mach-rtk119x/driver/dc2vo/fpga/include/iso_reg.h register defines.
>>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Thanks. Will patches 1-2 go through some watchdog tree, or should I
queue them in my Realtek tree now?
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-09-10 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 23:15 [PATCH v2 0/3] arm64: Realtek RTD1295 watchdog Andreas Färber
2017-09-04 23:16 ` [PATCH v2 1/3] dt-bindings: watchdog: Add Realtek RTD1295 Andreas Färber
2017-09-10 15:17 ` Guenter Roeck
2017-09-04 23:16 ` [PATCH v2 2/3] " Andreas Färber
2017-09-10 15:17 ` Guenter Roeck
2017-09-10 16:24 ` Andreas Färber [this message]
2017-09-04 23:16 ` [PATCH v2 3/3] arm64: dts: realtek: Add watchdog node for RTD1295 Andreas Färber
2017-09-10 15:18 ` Guenter Roeck
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=155916fd-1689-9a59-3e7c-9e9768a98057@suse.de \
--to=afaerber@suse.de \
--cc=hepeng@zidoo.tv \
--cc=jiang.liqin@geniatech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®