From: Oren Weil <oren.jer.weil@intel.com>
To: gregkh@suse.de
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org, alan@linux.intel.com,
wim@iguana.be, tomas.winkler@intel.com,
Oren Weil <oren.jer.weil@intel.com>
Subject: [PATCH 00/12] staging: mei: adding new watchdog core support
Date: Wed, 31 Aug 2011 16:42:36 +0300 [thread overview]
Message-ID: <1314798168-15613-1-git-send-email-oren.jer.weil@intel.com> (raw)
In this patches set we are adding the new watchdog core to the mei driver.
Until now the mei driver manage by itself the Intel(R) Active Management Technology
(Intel(R) AMT) watchdog, the driver send the heartbeat by a
internal timer and the internal was defined by module parameter.
for more information about the Intel(R) AMT watchdog read
drivers/staging/mei/mei.txt
Oren Weil (12):
staging: mei: removing dependency between WD and AMTHI init function.
staging: mei: fix register access function comments
staging: mei: registering the MEI driver with the kernel watchdog
core interface
staging: mei: adding watchdog ops
staging: mei: adding watchdog ping
staging: mei: adding set_timeout watchdog function
staging: mei: renaming delayed work field and function to a
meaningful name.
staging: mei: resuming timer regardless of the watchdog timeout
value.
stagign: mei: client init code cleanup
staging: mei: removing wd module parameters
staging: mei: adding mei_wd_stop function comment
staging: mei: adding watchdog core dependency to kconfig
drivers/staging/mei/Kconfig | 2 +-
drivers/staging/mei/init.c | 9 ++-
drivers/staging/mei/interface.h | 8 +-
drivers/staging/mei/interrupt.c | 45 +++-----
drivers/staging/mei/main.c | 19 ++--
drivers/staging/mei/mei_dev.h | 22 +++-
drivers/staging/mei/wd.c | 241 ++++++++++++++++++++++++++++++++------
7 files changed, 260 insertions(+), 86 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-08-31 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 13:42 Oren Weil [this message]
2011-08-31 13:42 ` [PATCH 01/12] staging: mei: removing dependency between WD and AMTHI init function Oren Weil
2011-08-31 13:42 ` [PATCH 02/12] staging: mei: fix register access function comments Oren Weil
2011-08-31 13:42 ` [PATCH 03/12] staging: mei: registering the MEI driver with the kernel watchdog core interface Oren Weil
2011-08-31 13:42 ` [PATCH 04/12] staging: mei: adding watchdog ops Oren Weil
2011-08-31 13:42 ` [PATCH 05/12] staging: mei: adding watchdog ping Oren Weil
2011-08-31 16:52 ` Dan Carpenter
2011-09-06 23:48 ` Greg KH
2011-08-31 13:42 ` [PATCH 06/12] staging: mei: adding set_timeout watchdog function Oren Weil
2011-08-31 13:42 ` [PATCH 07/12] staging: mei: renaming delayed work field and function to a meaningful name Oren Weil
2011-08-31 13:42 ` [PATCH 08/12] staging: mei: resuming timer regardless of the watchdog timeout value Oren Weil
2011-08-31 13:42 ` [PATCH 09/12] stagign: mei: client init code cleanup Oren Weil
2011-08-31 13:42 ` [PATCH 10/12] staging: mei: removing wd module parameters Oren Weil
2011-08-31 13:42 ` [PATCH 11/12] staging: mei: adding mei_wd_stop function comment Oren Weil
2011-08-31 13:42 ` [PATCH 12/12] staging: mei: adding watchdog core dependency to kconfig Oren Weil
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=1314798168-15613-1-git-send-email-oren.jer.weil@intel.com \
--to=oren.jer.weil@intel.com \
--cc=alan@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=tomas.winkler@intel.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;
as well as URLs for NNTP newsgroup(s).