From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Kilkenny <akilkenny@xes-inc.com>, wim@iguana.be
Cc: khollis@bitgate.com, linux-standards@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Watchdog API Update
Date: Sat, 2 Jun 2007 10:12:02 -0700 [thread overview]
Message-ID: <20070602101202.9d118c44.randy.dunlap@oracle.com> (raw)
In-Reply-To: <46606CBA.9020904@xes-inc.com>
On Fri, 01 Jun 2007 14:00:10 -0500 Andrew Kilkenny wrote:
> Patched from 2.6.16
>
> Included are patches for the Watchdog API. This API is already AD HOC
> according to the documentation, so the update is not expected to meet
> much opposition.
>
> The patch/api update adds support for enabling watchdog monitoring
> directly via the kernel driver. It appears some drivers do this on their
> own, while others implement the api, dictating that userspace programs
> manage the watchdog. This includes adding both the ability for userspace
> to enable/disable the feature, and to compile in the feature to be
> enabled automatically at boot.
>
> The Patch file includes diffs from watchdog.h, the watchdog.txt
> documentation, and a KConfig file.
what patch file??
> I am unsure on the licensing information. The header file only mentions
> it was derived from Ken's original code. GPL information is absent,
> along with dates. In fact, I am unsure where the copyright belongs, if
> it defaults to Berkshire PC, if it must be GPL, and the like. Guidance
> will be greatly appreciated, especially if (absent a GPL declaration) I
> need permission to handle this code.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-06-02 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 19:00 Andrew Kilkenny
2007-06-02 17:12 ` Randy Dunlap [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=20070602101202.9d118c44.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akilkenny@xes-inc.com \
--cc=khollis@bitgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-standards@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
all inboxes | Powered by JetHome®