From: wim@www.linux-watchdog.org
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Igor Pylypiv <igor.pylypiv@gmail.com>,
Jayachandran C <jnair@caviumnetworks.com>,
Jerry Hoemann <jerry.hoemann@hpe.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: [GIT PULL REQUEST] watchdog - v4.16 Fixes 2
Date: Sat, 10 Mar 2018 11:44:09 +0100 [thread overview]
Message-ID: <20180310104409.GA3963@www.linux-watchdog.org> (raw)
Hi Linus,
Please pull the watchdog fixes for the v4.16 release cycle.
This series contains:
* f71808e_wdt: Fix magic close handling
* sbsa: 32-bit read fix for WCV
* hpwdt: Remove legacy NMI sourcing
The output from git request-pull:
----------------------------------------------------------------
The following changes since commit a17f4f032b61abd998a1f81b206a4517e2e3db2f:
watchdog: sp5100_tco.c: fix potential build failure (2018-02-19 17:44:05 +0100)
are available in the git repository at:
git://www.linux-watchdog.org/linux-watchdog.git tags/linux-watchdog-4.16-fixes-2
for you to fetch changes up to 2b3d89b402b085b08498e896c65267a145bed486:
watchdog: hpwdt: Remove legacy NMI sourcing. (2018-03-03 15:52:33 +0100)
----------------------------------------------------------------
linux-watchdog 4.16-fixes-2 merge window tag
----------------------------------------------------------------
Igor Pylypiv (1):
watchdog: f71808e_wdt: Fix magic close handling
Jayachandran C (1):
watchdog: sbsa: use 32-bit read for WCV
Jerry Hoemann (1):
watchdog: hpwdt: Remove legacy NMI sourcing.
drivers/watchdog/f71808e_wdt.c | 3 +-
drivers/watchdog/hpwdt.c | 501 +----------------------------------------
drivers/watchdog/sbsa_gwdt.c | 3 +-
3 files changed, 13 insertions(+), 494 deletions(-)
reply other threads:[~2018-03-10 10:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180310104409.GA3963@www.linux-watchdog.org \
--to=wim@www.linux-watchdog.org \
--cc=akpm@linux-foundation.org \
--cc=igor.pylypiv@gmail.com \
--cc=jerry.hoemann@hpe.com \
--cc=jnair@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=torvalds@linux-foundation.org \
--cc=wim@linux-watchdog.org \
/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.