From: Wim Van Sebroeck <wim@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>,
Jiangshan Yi <yijiangshan@kylinos.cn>,
Manank Patel <pmanank200502@gmail.com>
Subject: [GIT PULL REQUEST] watchdog - v6.1 release cycle.
Date: Tue, 1 Nov 2022 09:19:02 +0100 [thread overview]
Message-ID: <20221101081902.GA5794@www.linux-watchdog.org> (raw)
Hi Linus,
Please pull following watchdog changes for the v6.1-rc4 release cycle.
This series contains:
* exar_wdt.c fix use after free
The output from git request-pull:
----------------------------------------------------------------
The following changes since commit e25b091bed4946078c0998e4be77bc56824a9adf:
watchdog: Add tracing events for the most usual watchdog events (2022-10-12 09:47:02 +0200)
are available in the git repository at:
git://www.linux-watchdog.org/linux-watchdog.git tags/linux-watchdog-6.1-rc4
for you to fetch changes up to 82ebbe65d781064cfb0a6a8af221a9cebcaaac9e:
drivers: watchdog: exar_wdt.c fix use after free (2022-10-19 19:49:47 +0200)
----------------------------------------------------------------
linux-watchdog 6.1-rc4 tag
----------------------------------------------------------------
Jiangshan Yi (1):
watchdog: sp805_wdt: fix spelling typo in comment
Manank Patel (1):
drivers: watchdog: exar_wdt.c fix use after free
drivers/watchdog/exar_wdt.c | 4 +++-
drivers/watchdog/sp805_wdt.c | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
----------------------------------------------------------------
Kind regards,
Wim.
next reply other threads:[~2022-11-01 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 8:19 Wim Van Sebroeck [this message]
2022-11-01 19:32 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-10-12 7:42 Wim Van Sebroeck
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=20221101081902.GA5794@www.linux-watchdog.org \
--to=wim@linux-watchdog.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pmanank200502@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=yijiangshan@kylinos.cn \
/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®