devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>
Cc: devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com,
	p.zabel@pengutronix.de, linux-kernel@vger.kernel.org,
	linux@roeck-us.net, linux-mediatek@lists.infradead.org,
	runyang.chen@mediatek.com, matthias.bgg@gmail.com,
	robh+dt@kernel.org, wim@linux-watchdog.org
Subject: Re: [PATCH 1/4] dt-bindings: watchdog: Add compatible for MediaTek MT8186
Date: Fri, 25 Feb 2022 10:24:55 -0600	[thread overview]
Message-ID: <YhkC17tHJbd5Sd6J@robh.at.kernel.org> (raw)
In-Reply-To: <20220216014505.28428-2-rex-bc.chen@mediatek.com>

On Wed, 16 Feb 2022 09:45:02 +0800, Rex-BC Chen wrote:
> Add dt-binding documentation of watchdog for MediaTek MT8186 SoC.
> 
> Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com>
> ---
>  Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 1 +
>  1 file changed, 1 insertion(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-02-25 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220216014505.28428-1-rex-bc.chen@mediatek.com>
2022-02-16  1:45 ` [PATCH 1/4] dt-bindings: watchdog: Add compatible for MediaTek MT8186 Rex-BC Chen
2022-02-25 16:24   ` Rob Herring [this message]
2022-02-25 16:36   ` Guenter Roeck
2022-02-16  1:45 ` [2/4] dt-bindings: reset: mt8186: add toprgu reset-controller header file Rex-BC Chen
2022-02-25 16:25   ` Rob Herring
2022-02-25 16:37   ` Guenter Roeck
2022-03-01  2:56     ` Rex-BC Chen
2022-02-16  1:45 ` [3/4] dt-bindings: reset: mt8186: add DSI reset bit for MMSYS Rex-BC Chen
2022-02-25 16:26   ` Rob Herring
2022-03-01  2:54     ` Rex-BC Chen
2022-02-16  1:45 ` [4/4] watchdog: mediatek: mt8186: add wdt support Rex-BC Chen
2022-02-25 16:36   ` Guenter Roeck
2022-02-16  2:45 ` [0/4] Add watchdog support for MT8186 SoC Macpaul Lin

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=YhkC17tHJbd5Sd6J@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.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=p.zabel@pengutronix.de \
    --cc=rex-bc.chen@mediatek.com \
    --cc=robh+dt@kernel.org \
    --cc=runyang.chen@mediatek.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).