From: Guenter Roeck <linux@roeck-us.net>
To: michaelsh@mellanox.com, wim@linux-watchdog.org,
andy@infradead.org, dvhart@infradead.org
Cc: linux-watchdog@vger.kernel.org,
platform-driver-x86@vger.kernel.org, vadimp@mellanox.com
Subject: Re: [PATCH v4 0/4] support watchdog with longer timeout period
Date: Tue, 5 May 2020 09:09:03 -0700 [thread overview]
Message-ID: <ac2c580c-7cc0-8091-f3bc-fce175478e50@roeck-us.net> (raw)
In-Reply-To: <20200504141427.17685-1-michaelsh@mellanox.com>
On 5/4/20 7:14 AM, michaelsh@mellanox.com wrote:
> From: Michael Shych <michaelsh@mellanox.com>
>
> This patchset adds support of extended new watchdog type 3 of Mellanox
> Ethernet and Infiniband switch systems.
> This type of watchdog can have a timeout period longer than 255 or 32 sec.
> as it was before.
>
> Michael Shych (4):
> platform_data/mlxreg: support new watchdog type with longer timeout
> period
> platform/x86: mlx-platform: support new watchdog type with longer
> timeout
> watchdog: mlx-wdt: support new watchdog type with longer timeout
> period
> docs: watchdog: mlx-wdt: Add description of new watchdog type 3
>
> Documentation/watchdog/mlx-wdt.rst | 10 ++++
> drivers/platform/x86/mlx-platform.c | 106 ++++++++++++++++++++++++++++++
> drivers/watchdog/mlx_wdt.c | 73 ++++++++++++++++++++----
> include/linux/platform_data/mlxreg.h | 5 +-
> 4 files changed, 182 insertions(+), 12 deletions(-)
>
Guess the big question is now which branch to use to take this series.
Thoughts, anyone ?
Guenter
next prev parent reply other threads:[~2020-05-05 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 14:14 [PATCH v4 0/4] support watchdog with longer timeout period michaelsh
2020-05-04 14:14 ` [PATCH v4 1/4] platform_data/mlxreg: support new watchdog type " michaelsh
2020-05-04 14:14 ` [PATCH v4 2/4] platform/x86: mlx-platform: support new watchdog type with longer timeout michaelsh
2020-05-04 14:14 ` [PATCH v4 3/4] watchdog: mlx-wdt: support new watchdog type with longer timeout period michaelsh
2020-05-05 16:07 ` Guenter Roeck
2020-05-04 14:14 ` [PATCH v4 4/4] docs: watchdog: mlx-wdt: Add description of new watchdog type 3 michaelsh
2020-05-05 16:08 ` Guenter Roeck
2020-05-05 16:09 ` Guenter Roeck [this message]
2020-05-05 16:14 ` [PATCH v4 0/4] support watchdog with longer timeout period Andy Shevchenko
2020-05-05 18:39 ` Vadim Pasternak
2020-05-05 20:24 ` Andy Shevchenko
2020-05-21 14:25 ` Michael Shych
2020-05-29 23:12 ` Guenter Roeck
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=ac2c580c-7cc0-8091-f3bc-fce175478e50@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=michaelsh@mellanox.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@mellanox.com \
--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).