From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Chew <achew@nvidia.com>
Cc: wim@iguana.be, rob@landley.net, swarren@wwwdotorg.org,
thierry.reding@gmail.com, grant.likely@linaro.org,
robh+dt@kernel.org, abrestic@chromium.org, dgreid@chromium.org,
katierh@chromium.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v7 1/1] watchdog: Add tegra watchdog
Date: Fri, 14 Feb 2014 12:14:09 -0800 [thread overview]
Message-ID: <20140214201409.GA31748@roeck-us.net> (raw)
In-Reply-To: <1392408185-15387-1-git-send-email-achew@nvidia.com>
Hi Andrew,
On Fri, Feb 14, 2014 at 12:03:05PM -0800, Andrew Chew wrote:
> Add a driver for the hardware watchdogs in NVIDIA Tegra SoCs (Tegra30 and
> later). This driver will configure one watchdog timer that will reset the
> system in the case of a watchdog timeout.
>
> This driver binds to the nvidia,tegra30-timer device node and gets its
> register base from there.
>
> Signed-off-by: Andrew Chew <achew@nvidia.com>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> Tested-by: Stephen Warren <swarren@nvidia.com>
> Reviewed-by: Stephen Warren <swarren@nvidia.com>
> ---
> Changes from v6:
>
> Removed kref stuff. We can't think of why it's needed here.
>
Me likes that :-)
Many changes since my original review, but I re-confirm my Reviewed-by: above.
Guenter
next prev parent reply other threads:[~2014-02-14 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 20:03 [PATCH v7 1/1] watchdog: Add tegra watchdog Andrew Chew
2014-02-14 20:14 ` Guenter Roeck [this message]
2014-03-02 11:51 ` Wim Van Sebroeck
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=20140214201409.GA31748@roeck-us.net \
--to=linux@roeck-us.net \
--cc=abrestic@chromium.org \
--cc=achew@nvidia.com \
--cc=dgreid@chromium.org \
--cc=grant.likely@linaro.org \
--cc=katierh@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--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