linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 王擎 <wangqing@vivo.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
	Rob Herring <robh+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re:[PATCH V9 0/2] watchdog: mtk: support pre-timeout when the bark irq is available
Date: Wed, 28 Apr 2021 09:51:58 +0800 (GMT+08:00)	[thread overview]
Message-ID: <ADUA9AALDva0XEeX2p71l4rW.3.1619574718914.Hmail.wangqing@vivo.com> (raw)
In-Reply-To: <1619315527-8171-1-git-send-email-wangqing@vivo.com>


>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(-)
>
>-- 
>2.7.4
>

Hi Guenter:
Please help review this version, if there is no problem, 
can you pick up to the next branch?

Thanks,
Qing


      parent reply	other threads:[~2021-04-28  1:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25  1:52 [PATCH V9 0/2] watchdog: mtk: support pre-timeout when the bark irq is available Wang Qing
2021-04-25  1:52 ` [PATCH V9 1/2] " Wang Qing
2021-04-29 22:22   ` Guenter Roeck
2021-05-06  1:51     ` 王擎
2021-05-06  2:10       ` Guenter Roeck
2021-04-25  1:52 ` [PATCH V9 2/2] doc: mtk-wdt: " Wang Qing
2021-04-29 21:46   ` Rob Herring
2021-04-28  1:51 ` 王擎 [this message]

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=ADUA9AALDva0XEeX2p71l4rW.3.1619574718914.Hmail.wangqing@vivo.com \
    --to=wangqing@vivo.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.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).