From: "Chhao Chang (常浩)" <ot_chhao.chang@mediatek.com>
To: "linus.walleij@linaro.org" <linus.walleij@linaro.org>
Cc: "Chunhui Li (李春辉)" <chunhui.li@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wenbin Mei (梅文彬)" <Wenbin.Mei@mediatek.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"sean.wang@kernel.org" <sean.wang@kernel.org>,
"Hanks Chen (陳彥廷)" <Hanks.Chen@mediatek.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"Qingliang Li (黎晴亮)" <Qingliang.Li@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Axe Yang (杨磊)" <Axe.Yang@mediatek.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v4 0/3] Add EINT support for multiple addresses
Date: Sat, 22 Mar 2025 03:22:55 +0000 [thread overview]
Message-ID: <94250d48cbb9750ad9cdfff1ddf9d60c3b70a6f1.camel@mediatek.com> (raw)
In-Reply-To: <CACRpkdYSNMV2jymbHaxRp-PmzbbkEJ_eUcT20whYw3gdhEGOGg@mail.gmail.com>
On Fri, 2025-03-14 at 10:58 +0100, Linus Walleij wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> Hi Hao,
>
> thanks for your patches!
>
> On Tue, Feb 25, 2025 at 3:07 PM Hao Chang <
> ot_chhao.chang@mediatek.com> wrote:
>
> > This patch depends on
> > [v3,2/2] pinctrl: mediatek: add mt8196 driver
> > [v3,1/2] dt-bindings: pinctrl: mediatek: add support for mt8196
> >
> > Please also accept this patch together with [1]
> > to avoid build and dt binding check error.
> > [1]
> > https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=&submitter=215008&state=&q=v3&archive=&delegate=__;!!CTRNKA9wMg0ARbw!gUMnwvZLiv7PLfBynupfezUYGOwSWFXcCubh-tJn4vobCnaiSRRXRgakWcQBdoQ8s0VNcBoQUpuFFhlLgtJb-OArDwfJKcQ$
>
> Since the dependence series is not finished I can't apply these
> patches either, do you want to send an independent version of these
> patches so we merge them *first* since they seem finished?
>
> Then the mt8196 series can rebase on your patches in v6.15-rc1
> instead.
>
> Just send a version based on v6.14-rc1 and I will apply it.
Thanks for your suggestion, I will fix this.
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2025-03-22 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 14:07 [PATCH v4 0/3] Add EINT support for multiple addresses Hao Chang
2025-02-25 14:07 ` [PATCH v4 1/3] pinctrl: mediatek: add eint pins Hao Chang
2025-02-25 14:07 ` [PATCH v4 2/3] pinctrl: mediatek: modify the method of obtaining eint address Hao Chang
2025-02-25 14:07 ` [PATCH v4 3/3] pinctrl: mediatek: adapt to EINT multi-segment addresses Hao Chang
2025-03-14 9:58 ` [PATCH v4 0/3] Add EINT support for multiple addresses Linus Walleij
2025-03-22 3:22 ` Chhao Chang (常浩) [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=94250d48cbb9750ad9cdfff1ddf9d60c3b70a6f1.camel@mediatek.com \
--to=ot_chhao.chang@mediatek.com \
--cc=Axe.Yang@mediatek.com \
--cc=Hanks.Chen@mediatek.com \
--cc=Qingliang.Li@mediatek.com \
--cc=Wenbin.Mei@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunhui.li@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@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).