From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@iguana.be>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
linux-watchdog@vger.kernel.org, Fu Wei <fu.wei@linaro.org>
Subject: Re: Additional patches in my watchdog-next branch
Date: Tue, 29 Dec 2015 17:37:05 +0100 [thread overview]
Message-ID: <20151229173705.1596cf1d@free-electrons.com> (raw)
In-Reply-To: <20151229160411.GB30405@roeck-us.net>
Hello,
On Tue, 29 Dec 2015 08:04:11 -0800, Guenter Roeck wrote:
> Hi Wim,
>
> On Tue, Dec 29, 2015 at 08:17:32AM +0100, Wim Van Sebroeck wrote:
> [ ... ]
> >
> > SBSA: What should be done is to create a correct driver without pretimeout and with just the normal watchdog (=reboot if we aren't kicked fast enough) behaviour and get that in.
> >
> Absoutely agree.
Sorry to get into the conversation, but I got interested into the SBSA
watchdog driver recently, and looked at the status of its merge in the
kernel.
I've looked at Fu Wei's v9 from November which I believe is the latest
version, and then looked at Vladimir's generic pretimeout patch set.
Vladimir, do you plan to rework the SBSA watchdog driver on top of your
pretimeout patch series ? Or do Fu Wei intends do it ? Alternatively,
as suggested by Wim and Guenter, submitting an initial version without
pretimeout support would be a good thing. Are you, or Fu, interested in
doing this, or should I work at updating Fu's patches in this
direction ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-29 16:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 15:23 Additional patches in my watchdog-next branch Guenter Roeck
2015-12-28 15:27 ` Wim Van Sebroeck
2015-12-28 21:57 ` Guenter Roeck
2015-12-28 22:54 ` Wim Van Sebroeck
2015-12-28 23:17 ` Vladimir Zapolskiy
2015-12-29 7:17 ` Wim Van Sebroeck
2015-12-29 16:04 ` Guenter Roeck
2015-12-29 16:37 ` Thomas Petazzoni [this message]
2015-12-29 17:28 ` Guenter Roeck
2015-12-30 9:44 ` Thomas Petazzoni
2015-12-30 13:30 ` Fu Wei
2015-12-30 14:02 ` Thomas Petazzoni
2015-12-30 15:01 ` Fu Wei
2015-12-30 15:03 ` Thomas Petazzoni
2015-12-30 15:06 ` Fu Wei
2015-12-30 11:44 ` Fu Wei
2015-12-30 11:30 ` Fu Wei
2016-01-03 22:49 ` Vladimir Zapolskiy
2015-12-29 0:08 ` Guenter Roeck
2015-12-29 7:21 ` Wim Van Sebroeck
2015-12-29 16:02 ` Guenter Roeck
2015-12-29 20:01 ` Wim Van Sebroeck
2015-12-29 21:20 ` Guenter Roeck
2015-12-30 10:06 ` 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=20151229173705.1596cf1d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=fu.wei@linaro.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=vladimir_zapolskiy@mentor.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