From: Corey Minyard <minyard@acm.org>
To: Don Zickus <dzickus@redhat.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
openipmi-developer@lists.sourceforge.net,
linux-watchdog@vger.kernel.org
Subject: Re: ipmi watchdog questions
Date: Fri, 02 May 2014 21:51:56 -0500 [thread overview]
Message-ID: <536459CC.4090302@acm.org> (raw)
In-Reply-To: <20140503021002.GA20778@redhat.com>
On 05/02/2014 09:10 PM, Don Zickus wrote:
> framework.
> Implementing read/poll should be easy in the framework.
>
> Don, are you interested in working on this? i won't be able to get to
> it for a bit.
> I don't mind doing the work, as long as we agree on an implementation. :-)
>
> Just throwing an idea out there based on Guenter's reply, should I just
> create a new file ipmi_wdt in the drivers/watchdog area that is ported to
> the new watchdog framework?
Yes, that's what I would do. I definitely belongs in the watchdog
directory.
>
> The idea is if a user pops up that wants the userspace solution that can
> fallback to the old ipmi_watchdog currently implemented. Otherwise the
> new port would be the recommended way to go? Seeing that the current
> driver is updated fairly infrequent, keeping both drivers in sync wouldn't
> be to hard.
>
> Just a random idea.
Yes, that's probably a good plan.
-corey
next prev parent reply other threads:[~2014-05-03 2:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 13:58 ipmi watchdog questions Don Zickus
2014-05-02 0:38 ` Corey Minyard
2014-05-02 1:11 ` Guenter Roeck
2014-05-02 4:38 ` Corey Minyard
2014-05-02 13:17 ` Guenter Roeck
2014-05-02 16:44 ` Don Zickus
2014-05-02 17:18 ` Guenter Roeck
2014-05-02 17:46 ` Don Zickus
2014-05-02 21:52 ` Corey Minyard
2014-05-02 23:20 ` Guenter Roeck
2014-05-03 2:10 ` Don Zickus
2014-05-03 2:51 ` Corey Minyard [this message]
2014-05-03 4:23 ` Guenter Roeck
2014-05-02 15:10 ` Don Zickus
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=536459CC.4090302@acm.org \
--to=minyard@acm.org \
--cc=dzickus@redhat.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openipmi-developer@lists.sourceforge.net \
/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.