linux-mediatek.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Fengquan Chen <Fengquan.Chen@mediatek.com>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-watchdog@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: tinghan.shen@mediatek.com, randy.wu@mediatek.com,
	rex-bc.chen@mediatek.com, christine.zhu@mediatek.com,
	joe.yang@mediatek.com, zhishuang.zhang@mediatek.com
Subject: Re: [PATCH] watchdog: mtk: add disable_wdt_extrst support
Date: Thu, 2 Sep 2021 06:39:11 -0700	[thread overview]
Message-ID: <4a7c1fa7-cd56-54c0-7b3c-ed48ec0e886d@roeck-us.net> (raw)
In-Reply-To: <1630569881-6032-1-git-send-email-Fengquan.Chen@mediatek.com>

On 9/2/21 1:04 AM, Fengquan Chen wrote:
> From: "fengquan.chen" <fengquan.chen@mediatek.com>
> 
> In some cases, we may need watchdog just to trigger an
> internal soc reset without sending any output signal.
> 
> Provide a disable_wdt_extrst parameter for configuration.
> We can disable or enable it just by configuring dts.
> 
> fengquan.chen (1):
>    watchdog: mtk: add disable_wdt_extrst support
> 
>   drivers/watchdog/mtk_wdt.c | 7 +++++++
>   1 file changed, 7 insertions(+)
> 

A single patch does not require an introductory e-mail.
Also, if provided, it needed to be numbered (PATCH 0/1)
to distinguish it from the actual patch.

Guenter

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

      parent reply	other threads:[~2021-09-02 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02  8:04 [PATCH] watchdog: mtk: add disable_wdt_extrst support Fengquan Chen
2021-09-02  8:04 ` Fengquan Chen
2021-09-02 13:43   ` Guenter Roeck
2021-09-03  6:51     ` Fengquan Chen
2021-09-02 13:39 ` Guenter Roeck [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=4a7c1fa7-cd56-54c0-7b3c-ed48ec0e886d@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Fengquan.Chen@mediatek.com \
    --cc=christine.zhu@mediatek.com \
    --cc=joe.yang@mediatek.com \
    --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=matthias.bgg@gmail.com \
    --cc=randy.wu@mediatek.com \
    --cc=rex-bc.chen@mediatek.com \
    --cc=tinghan.shen@mediatek.com \
    --cc=wim@linux-watchdog.org \
    --cc=zhishuang.zhang@mediatek.com \
    /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).