From: Matthias Brugger <matthias.bgg@gmail.com>
To: Julius Werner <jwerner@chromium.org>,
Douglas Anderson <dianders@chromium.org>
Cc: Marc Zyngier <maz@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
wenst@chromium.org, Eddie Huang <eddie.huang@mediatek.com>,
Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Ben Ho <Ben.Ho@mediatek.com>, Weiyi Lu <weiyi.lu@mediatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-arm-kernel@lists.infradead.org,
Tinghan Shen <tinghan.shen@mediatek.com>,
Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
yidilin@chromium.org, Seiya Wang <seiya.wang@mediatek.com>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] dt-bindings: interrupt-controller: arm,gic-v3: Add quirk for Mediatek SoCs w/ broken FW
Date: Fri, 12 May 2023 13:32:01 +0200 [thread overview]
Message-ID: <cdcf000e-d1f4-d420-3151-0c8fe1b534d5@gmail.com> (raw)
In-Reply-To: <CAODwPW8TqhArafCK3RvBdxyiav3WL=0MU6x=QyBOFP-h8bQrWw@mail.gmail.com>
Hi Julius,
On 12/05/2023 00:37, Julius Werner wrote:
> Reviewed-by: Julius Werner <jwerner@chromium.org>
For the future please don't delete the patch itself if you give a tag, just
leave it as it is (and don't top-post your tag :) )
Regards,
Matthias
next prev parent reply other threads:[~2023-05-12 11:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 22:05 [PATCH 0/6] irqchip/gic-v3: Disable pseudo NMIs on Mediatek Chromebooks w/ bad FW Douglas Anderson
2023-05-11 22:05 ` [PATCH 1/6] dt-bindings: interrupt-controller: arm,gic-v3: Add quirk for Mediatek SoCs w/ broken FW Douglas Anderson
2023-05-11 22:37 ` Julius Werner
2023-05-12 11:32 ` Matthias Brugger [this message]
2023-05-12 8:02 ` Marc Zyngier
2023-05-12 13:40 ` Doug Anderson
2023-05-11 22:05 ` [PATCH 2/6] irqchip/gic-v3: Disable pseudo NMIs on Mediatek devices w/ firmware issues Douglas Anderson
2023-05-11 22:38 ` Julius Werner
2023-05-11 22:05 ` [PATCH 3/6] arm64: dts: mediatek: mt8183: Add mediatek,gicr-save-quirk Douglas Anderson
2023-05-11 22:38 ` Julius Werner
2023-05-12 8:13 ` Marc Zyngier
2023-05-12 14:15 ` Doug Anderson
2023-05-15 11:29 ` AngeloGioacchino Del Regno
2023-05-11 22:05 ` [PATCH 4/6] arm64: dts: mediatek: mt8186: " Douglas Anderson
2023-05-11 22:38 ` Julius Werner
2023-05-11 22:05 ` [PATCH 5/6] arm64: dts: mediatek: mt8192: " Douglas Anderson
2023-05-11 22:38 ` Julius Werner
2023-05-11 22:05 ` [PATCH 6/6] arm64: dts: mediatek: mt8195: " Douglas Anderson
2023-05-11 22:38 ` Julius Werner
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=cdcf000e-d1f4-d420-3151-0c8fe1b534d5@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Ben.Ho@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=eddie.huang@mediatek.com \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=jwerner@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=seiya.wang@mediatek.com \
--cc=tglx@linutronix.de \
--cc=tinghan.shen@mediatek.com \
--cc=weiyi.lu@mediatek.com \
--cc=wenst@chromium.org \
--cc=yidilin@chromium.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).