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>, Arnd Bergmann <arnd@arndb.de>,
Matteo Croce <mcroce@redhat.com>,
Radu Rendec <radu.rendec@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: [GIT PULL REQUEST] watchdog - v4.16 Fixes
Date: Sat, 3 Mar 2018 10:22:02 +0100 [thread overview]
Message-ID: <20180303092202.GA29051@www.linux-watchdog.org> (raw)
Hi Linus,
Please pull the watchdog fixes for the v4.16 release cycle.
This series contains:
* rave-sp: add NVMEM dependency
* Build fixes for i6300esb_wdt, xen_wdt and sp5100_tco
The output from git request-pull:
----------------------------------------------------------------
The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51:
Linux 4.16-rc2 (2018-02-18 17:29:42 -0800)
are available in the git repository at:
git://www.linux-watchdog.org/linux-watchdog.git tags/linux-watchdog-4.16-fixes-1
for you to fetch changes up to a17f4f032b61abd998a1f81b206a4517e2e3db2f:
watchdog: sp5100_tco.c: fix potential build failure (2018-02-19 17:44:05 +0100)
----------------------------------------------------------------
linux-watchdog 4.16-fixes-1 merge window tag
----------------------------------------------------------------
Arnd Bergmann (1):
watchdog: rave-sp: add NVMEM dependency
Matteo Croce (1):
watchdog: i6300esb: fix build failure
Radu Rendec (1):
watchdog: xen_wdt: fix potential build failure
Wim Van Sebroeck (1):
watchdog: sp5100_tco.c: fix potential build failure
drivers/watchdog/Kconfig | 4 ++++
1 file changed, 4 insertions(+)
reply other threads:[~2018-03-03 9:32 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=20180303092202.GA29051@www.linux-watchdog.org \
--to=wim@www.linux-watchdog.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mcroce@redhat.com \
--cc=radu.rendec@gmail.com \
--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 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).