From: linux@roeck-us.net (Guenter Roeck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] watchdog: meson: Enable meson SoC specific data
Date: Tue, 24 Nov 2015 10:19:11 -0800 [thread overview]
Message-ID: <20151124181911.GA12289@roeck-us.net> (raw)
In-Reply-To: <CAOQ7t2bmNNTPxgZy4uZQF_u4yH2nxfMR_FqpKM0GavoUS9rRkA@mail.gmail.com>
On Wed, Nov 11, 2015 at 09:54:04AM +0100, Carlo Caione wrote:
> On Mon, Nov 9, 2015 at 4:03 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> > On 11/08/2015 04:18 AM, Carlo Caione wrote:
> >>
> >> From: Carlo Caione <carlo@endlessm.com>
> >>
> >> With this patch we refactor the driver code to enable watchdog support
> >> for all platforms based on Amlogic meson SoCs.
> >> The new default timeout is also now chosen considering the maximum
> >> timeout allowed by the SoC.
> >>
> >> Signed-off-by: Carlo Caione <carlo@endlessm.com>
> >
> >
> > Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>
> Wim,
> any (N)ACK on this?
>
Carlo,
Unless I missed it, we still don't have an Ack from a devicetree
maintainer for the devicetree changes.
Guenter
next prev parent reply other threads:[~2015-11-24 18:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 12:18 [PATCH v3 0/4] watchdog: meson: Add meson8b watchdog Carlo Caione
2015-11-08 12:18 ` [PATCH v3 1/4] watchdog: meson: Enable meson SoC specific data Carlo Caione
2015-11-09 15:03 ` Guenter Roeck
2015-11-11 8:54 ` Carlo Caione
2015-11-24 18:19 ` Guenter Roeck [this message]
2015-11-25 9:25 ` Carlo Caione
2015-11-25 14:20 ` Guenter Roeck
2015-11-08 12:18 ` [PATCH v3 2/4] watchdog: meson: Add meson8b " Carlo Caione
2015-11-09 15:03 ` Guenter Roeck
2015-11-08 12:18 ` [PATCH v3 3/4] Documentation: watchdog: Add new bindings for meson8b Carlo Caione
2015-11-09 15:07 ` Guenter Roeck
2015-11-08 12:18 ` [PATCH v3 4/4] ARM: dts: meson8b: Add watchdog node Carlo Caione
2015-11-09 15:11 ` 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=20151124181911.GA12289@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-arm-kernel@lists.infradead.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).