From: Krzysztof Kozlowski <krzk@kernel.org>
To: Runyang Chen <Runyang.Chen@mediatek.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
nfraprado@collabora.com
Cc: angelogioacchino.delregno@collabora.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 0/3] Add watchdog support for MT8188 Soc
Date: Wed, 21 Sep 2022 11:17:20 +0200 [thread overview]
Message-ID: <eec6e8b9-f39f-425a-4217-9c15b52600af@kernel.org> (raw)
In-Reply-To: <20220920105622.25666-1-Runyang.Chen@mediatek.com>
On 20/09/2022 12:56, Runyang Chen wrote:
> From: Runyang Chen <runyang.chen@mediatek.com>
>
> Based on tag: next-20220919, linux-next/master
>
> Refer to the discussion in the link:
> https://patchwork.kernel.org/project/linux-mediatek/patch/20220721014845.19044-2-allen-kh.cheng@mediatek.com/
> The other wdt compatible strings are unchanged.So, won't apply the
> series above
>
> v3:
> Rebase on 6.0-rc5 and add reviewed-by and acked-by tag.
If you rebased in, then why do you keep Ccing different address than one
in scripts/get_maintainers.pl?
Best regards,
Krzysztof
prev parent reply other threads:[~2022-09-21 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 10:56 [PATCH v3 0/3] Add watchdog support for MT8188 Soc Runyang Chen
2022-09-20 10:56 ` [PATCH v3 1/3] dt-bindings: watchdog: Add compatible for MediaTek MT8188 Runyang Chen
2022-09-20 12:27 ` AngeloGioacchino Del Regno
2022-09-20 10:56 ` [PATCH v3 2/3] dt-bindings: reset: mt8188: add toprgu reset-controller header file Runyang Chen
2022-09-20 12:26 ` AngeloGioacchino Del Regno
2022-09-20 10:56 ` [PATCH v3 3/3] watchdog: mediatek: mt8188: add wdt support Runyang Chen
2022-09-20 13:24 ` Matthias Brugger
2022-09-21 9:17 ` Krzysztof Kozlowski [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=eec6e8b9-f39f-425a-4217-9c15b52600af@kernel.org \
--to=krzk@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Runyang.Chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.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).