From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: chang hao <ot_chhao.chang@mediatek.com>,
matthias.bgg@gmail.com, sean.wang@kernel.org,
linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] v1 pinctrl: mtk-eint: add eint new design for mt8196
Date: Tue, 7 Jan 2025 16:54:27 +0100 [thread overview]
Message-ID: <ee926982-be21-4292-984b-57e0d777d3f9@collabora.com> (raw)
In-Reply-To: <CACRpkdarstoQW+ZBi+MWxEff_=h8bPo9+fwy=LW2uhWRuQ6YSQ@mail.gmail.com>
Il 07/01/25 16:11, Linus Walleij ha scritto:
> On Thu, Dec 19, 2024 at 1:39 PM AngeloGioacchino Del Regno
> <angelogioacchino.delregno@collabora.com> wrote:
>
>> Il 17/12/24 14:45, Linus Walleij ha scritto:
>>> Hi Chang,
>>>
>>> thanks for your patch!
>>>
>>> On Tue, Dec 3, 2024 at 2:13 PM chang hao <ot_chhao.chang@mediatek.com> wrote:
>>>
>>>> From: Chhao Chang <ot_chhao.chang@mediatek.com>
>>>>
>>>> Change 1: change EINT from 1 address to 5 addresses,
>>>> Eint number is stored on each base.
>>>> Change 2: Compatible with 1 address design
>>>>
>>>> Signed-off-by: Chhao Chang <ot_chhao.chang@mediatek.com>
>>>
>>> This patch looks good to me, as preparation for mt8196,
>>> but can one of the Mediatek experts please
>>> review it? If nothing happens I will just apply it I guess...
>>>
>>
>> Linus, that's something like the fourth time that he pushes variations of this
>> patch which do break all MediaTek SoCs in a way or another, leaving only MT8196
>> hopefully-functional.
>
> That's unfortunate, and I see there is some annoyance building
> up.
>
> The maintainers are here to protect the code and the change
> would have anyway just been reverted soon if it breaks stuff.
>
> How can we get this contribution on a better path?
>
> Chhao: maybe you can split your idea into smaller changes
> that can be reviewed and tested one by one?
>
Splitting would be nice, but I'm not sure it's really doable... besides,
there's only one way to get this right: testing on older platforms!
Even just one done manually, like MT8173, would be fine - the others can be
tested in KernelCI as we do have many MTK SoCs in the lab.
Then it's just about following the review process and adding the suggested
changes - nothing in particular.
Besides, I'm sorry for the very (maybe too much!) "strong" reply :-)
Cheers,
Angelo
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2025-01-07 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 13:12 chang hao
2024-12-17 13:45 ` Linus Walleij
2024-12-19 12:39 ` AngeloGioacchino Del Regno
2025-01-07 15:11 ` Linus Walleij
2025-01-07 15:54 ` AngeloGioacchino Del Regno [this message]
2024-12-19 12:38 ` AngeloGioacchino Del Regno
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=ee926982-be21-4292-984b-57e0d777d3f9@collabora.com \
--to=angelogioacchino.delregno@collabora.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=ot_chhao.chang@mediatek.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
all inboxes | Powered by JetHome®