linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wim Coekaerts <wim.coekaerts@oracle.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: wim@iguana.be, linux-watchdog@vger.kernel.org,
	sparclinux@vger.kernel.org
Subject: Re: [PATCH] watchdog: add sun4v_wdt device support
Date: Thu, 14 Jan 2016 08:27:00 -0800	[thread overview]
Message-ID: <5697CC54.1090808@oracle.com> (raw)
In-Reply-To: <20160113011231.GB22429@roeck-us.net>

On 1/12/16 5:12 PM, Guenter Roeck wrote:
> On Tue, Jan 12, 2016 at 03:10:32PM -0800, wim.coekaerts@oracle.com wrote:
>> From: Wim Coekaerts <wim.coekaerts@oracle.com>
>>
>> This adds a simple watchdog timer for the SPARC sunv4 architecture.
>> Export the sun4v_mach_set_watchdog() hv call, and add the target.
>> The driver was based on the same model used by the Xen watchdog driver.
>>
>> This was tested on T2, T4, T5 and T7.
>>
>> Signed-off-by: Wim Coekaerts <wim.coekaerts@oracle.com>
> Please use the watchdog subsystem for new drivers.
Ah wasn't clear that that was a requirement.. OK let me try and use the 
new subsystem instead.


  reply	other threads:[~2016-01-14 16:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 23:10 [PATCH] watchdog: add sun4v_wdt device support wim.coekaerts
2016-01-13  0:06 ` Julian Calaby
2016-01-13  1:12 ` Guenter Roeck
2016-01-14 16:27   ` Wim Coekaerts [this message]
2016-01-15 20:21 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2016-01-20 20:30 wim.coekaerts
2016-01-20 22:43 ` Julian Calaby
2016-01-20 23:19   ` Wim Coekaerts
2016-01-20 23:40     ` Julian Calaby
2016-01-20 23:45     ` Guenter Roeck
2016-01-21  1:35       ` Wim Coekaerts
2016-01-21  2:23         ` Julian Calaby
2016-01-21  2:36           ` Wim Coekaerts
2016-01-21  2:41             ` Julian Calaby
2016-01-20 23:37   ` Wim Coekaerts
2016-01-21 16:34 Guenter Roeck
2016-01-22 19:06 ` Wim Coekaerts

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=5697CC54.1090808@oracle.com \
    --to=wim.coekaerts@oracle.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sparclinux@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 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).