From: Yong Liang <yong.liang@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] amr64: dts: modify mt8183.dtsi
Date: Mon, 17 Feb 2020 18:14:53 +0800 [thread overview]
Message-ID: <1581934493.27500.4.camel@mhfsdcap03> (raw)
In-Reply-To: <b0345cfc-0e7c-65a8-5ff3-ea064b6c8905@gmail.com>
On Mon, 2020-02-17 at 18:05 +0800, Matthias Brugger wrote:
>
> On 17/02/2020 09:19, Yong Liang wrote:
> > From: "yong.liang" <yong.liang@mediatek.com>
> >
> > Add watchdog device node
> > Document base on http://lists.infradead.org/pipermail/linux-mediatek/2020-January/026415.html
> >
>
> Commit message shouldn't contain links to the mailinglist this is additional
> information just for review and should go after '---'
>
>
> > Signed-off-by: yong.liang <yong.liang@mediatek.com>
> > ---
>
> Next time please put reference to series your patches are based on here :)
>
> I fixed the commit message (the subject wasn't really usefull, I fixed that too)
> and pushed it to v5.6-next/dts64
>
> Thanks,
> Matthias
Hi Matthias:
So this patch confirmd to be merged?
Thansk you very much!
>
> > arch/arm64/boot/dts/mediatek/mt8183.dtsi | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> > index 10b32471bc7b..8b59e0eba2eb 100644
> > --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> > +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> > @@ -253,6 +253,13 @@
> > #interrupt-cells = <2>;
> > };
> >
> > + watchdog: watchdog@10007000 {
> > + compatible = "mediatek,mt8183-wdt",
> > + "mediatek,mt6589-wdt";
> > + reg = <0 0x10007000 0 0x100>;
> > + #reset-cells = <1>;
> > + };
> > +
> > apmixedsys: syscon@1000c000 {
> > compatible = "mediatek,mt8183-apmixedsys", "syscon";
> > reg = <0 0x1000c000 0 0x1000>;
> >
next prev parent reply other threads:[~2020-02-17 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Add watchdog device node>
2020-02-17 8:19 ` [PATCH 0/1] Add watchdog device node Yong Liang
2020-02-17 8:19 ` [PATCH 1/1] amr64: dts: modify mt8183.dtsi Yong Liang
2020-02-17 10:05 ` Matthias Brugger
2020-02-17 10:14 ` Yong Liang [this message]
2020-02-17 10:18 ` Matthias Brugger
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=1581934493.27500.4.camel@mhfsdcap03 \
--to=yong.liang@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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.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).