From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Chew <achew@nvidia.com>,
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
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 1/1] watchdog: Add tegra watchdog
Date: Thu, 06 Feb 2014 17:36:41 -0800 [thread overview]
Message-ID: <52F438A9.9000908@roeck-us.net> (raw)
In-Reply-To: <1391724356-17034-1-git-send-email-achew@nvidia.com>
On 02/06/2014 02:05 PM, 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>
> ---
Hi Andrew,
> +
> + /* This is the timer base. */
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + if (!res) {
> + dev_err(&pdev->dev, "incorrect resources\n");
> + return -ENODEV;
> + }
> +
I thought I mentioned that before - dem_iomap_resource() creates the
very same error message and returns an error if NULL is passed
as res argument to it. So the above error message (and error check)
is really redundant.
Thanks,
Guenter
next prev parent reply other threads:[~2014-02-07 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 22:05 [PATCH v4 1/1] watchdog: Add tegra watchdog Andrew Chew
2014-02-07 1:36 ` Guenter Roeck [this message]
[not found] ` <52F438A9.9000908-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-02-07 1:48 ` Andrew Chew
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=52F438A9.9000908@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