From: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
To: <mark-pk.tsai@mediatek.com>, <robh@kernel.org>
Cc: <alix.wu@mediatek.com>, <daniel@0x0f.com>,
<devicetree@vger.kernel.org>, <jason@lakedaemon.net>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
<maz@kernel.org>, <robh+dt@kernel.org>, <tglx@linutronix.de>,
<yj.chiang@mediatek.com>
Subject: Re: [PATCH 2/2] dt-bindings: interrupt-controller: Add MStar interrupt controller
Date: Wed, 2 Sep 2020 14:52:04 +0800 [thread overview]
Message-ID: <20200902065205.1971-1-mark-pk.tsai@mediatek.com> (raw)
In-Reply-To: <20200902063344.1852-3-mark-pk.tsai@mediatek.com>
Hi,
I've updated the yaml and post it in the patch series v3[1].
But I still keep the vendor specific property mstar,irqs-map-range as I
mentioned in the last reply.
Please review it.
[1] https://lore.kernel.org/lkml/20200902063344.1852-3-mark-pk.tsai@mediatek.com/
next prev parent reply other threads:[~2020-09-02 6:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 6:33 [PATCH v3 0/2] Add MStar interrupt controller support Mark-PK Tsai
2020-09-02 6:33 ` [PATCH v3 1/2] irqchip: irq-mst: " Mark-PK Tsai
2020-10-11 17:57 ` [tip: irq/core] irqchip/irq-mst: " tip-bot2 for Mark-PK Tsai
2020-09-02 6:33 ` [PATCH v3 2/2] dt-bindings: interrupt-controller: Add MStar interrupt controller Mark-PK Tsai
2020-09-02 6:52 ` Mark-PK Tsai [this message]
2020-09-14 20:07 ` Rob Herring
2020-10-11 17:57 ` [tip: irq/core] " tip-bot2 for Mark-PK Tsai
2020-09-13 15:59 ` [PATCH v3 0/2] Add MStar interrupt controller support Marc Zyngier
-- strict thread matches above, loose matches on Subject: below --
2020-08-19 3:42 [PATCH " Mark-PK Tsai
2020-08-19 3:42 ` [PATCH 2/2] dt-bindings: interrupt-controller: Add MStar interrupt controller Mark-PK Tsai
2020-08-25 21:48 ` Rob Herring
2020-08-26 7:50 ` Mark-PK Tsai
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=20200902065205.1971-1-mark-pk.tsai@mediatek.com \
--to=mark-pk.tsai@mediatek.com \
--cc=alix.wu@mediatek.com \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=yj.chiang@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).