[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210602104548.GC1865238@roeck-us.net>
Date: Wed, 2 Jun 2021 03:45:48 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Wang Qing <wangqing@...o.com>
Cc: Wim Van Sebroeck <wim@...ux-watchdog.org>,
Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V9,RESEND,0/2] watchdog: mtk: support pre-timeout when
the bark irq is available
On Mon, May 31, 2021 at 09:51:33AM +0800, Wang Qing wrote:
> Use the bark interrupt as the pretimeout notifier if available.
> The pretimeout notification shall occur at timeout-sec/2.
>
> Wang Qing (2):
> watchdog: mtk: support pre-timeout when the bark irq is available
> doc: mtk-wdt: support pre-timeout when the bark irq is available
>
> .../devicetree/bindings/watchdog/mtk-wdt.txt | 5 ++
> drivers/watchdog/mtk_wdt.c | 77 ++++++++++++++++++++--
> 2 files changed, 77 insertions(+), 5 deletions(-)
>
The series is already included in my watchdog-next branch, making this just
noise. On top of that, it is v2 without change log, meaning I have no idea
what changed since v1 and if it is different to the version I queued.
If it wasn't queued already, you'd get a message telling you to resubmit
with change log. As it is, I'll keep my version and drop this one.
Wim to decide what to do with it.
Guenter
Powered by blists - more mailing lists