From: Guenter Roeck <linux@roeck-us.net>
To: Kyle Roeschley <kyle.roeschley@ni.com>
Cc: david.madden@ni.com, joshc@ni.com,
linux-watchdog@vger.kernel.org, wim@iguana.be
Subject: Re: [PATCH v2] watchdog: ni9x3x_wdt: Add NI 903x/913x watchdog driver
Date: Fri, 19 Feb 2016 16:18:38 -0800 [thread overview]
Message-ID: <56C7B0DE.7070605@roeck-us.net> (raw)
In-Reply-To: <20160219171222.GA2072@senary>
On 02/19/2016 09:12 AM, Kyle Roeschley wrote:
> On Thu, Feb 18, 2016 at 09:27:05PM -0800, Guenter Roeck wrote:
>> On 02/18/2016 03:26 PM, Kyle Roeschley wrote:
>>> Add support for the watchdog timer on NI cRIO-903x and cDAQ-913x real-
>>> time controllers.
>>>
>>> Signed-off-by: Jeff Westfahl <jeff.westfahl@ni.com>
>>> Signed-off-by: Kyle Roeschley <kyle.roeschley@ni.com>
>>> ---
>>
>> This would be an optimal place for a change log.
>>
>> [ if any of my comments are duplicates, sorry, but a change log
>> would help avoiding that ]
>>
>
> Sorry about that, I'll make sure to do so in the future.
>
>>> Documentation/watchdog/watchdog-parameters.txt | 5 +
>>> drivers/watchdog/Kconfig | 11 +
>>> drivers/watchdog/Makefile | 1 +
>>> drivers/watchdog/ni9x3x_wdt.c | 274 +++++++++++++++++++++++++
>>
>> The name and context make me wonder: Is this driver going to support
>> all watchdog devices for NI9[0-9]3[0-9] ?
>>
>> If not, it may be better to select one supported device,
>> whatever that may be, for the name, and describe in Kconfig
>> and the documentation which devices the driver is known to support.
>>
>
> All of the 9[2-9]3[0-9] devices but the 963x do not and cannot run Linux,
> so they won't be a problem. There is already a driver for the 963x watchdog in
> our tree which is currently third in line for upstreaming, so that should be
> fine as well. That would lead me to think 9x3x is fine, but if not then 903x is
> fine.
>
Please use 903x, if you don't mind. After all, 9x3x _does_ include 963x
and is thus misleading.
Thanks,
Guenter
prev parent reply other threads:[~2016-02-20 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 23:26 [PATCH v2] watchdog: ni9x3x_wdt: Add NI 903x/913x watchdog driver Kyle Roeschley
2016-02-19 5:27 ` Guenter Roeck
2016-02-19 17:12 ` Kyle Roeschley
2016-02-20 0:18 ` Guenter Roeck [this message]
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=56C7B0DE.7070605@roeck-us.net \
--to=linux@roeck-us.net \
--cc=david.madden@ni.com \
--cc=joshc@ni.com \
--cc=kyle.roeschley@ni.com \
--cc=linux-watchdog@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.