From: "Justin Yeh (葉英茂)" <Justin.Yeh@mediatek.com>
To: "linusw@kernel.org" <linusw@kernel.org>
Cc: "sean.wang@kernel.org" <sean.wang@kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@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>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH v7 0/5] pinctrl: mediatek: Enable module build support
Date: Mon, 27 Jul 2026 05:08:09 +0000 [thread overview]
Message-ID: <9ca0e2e8a27262aa2c60b10b1ceec6b40a5dfa7c.camel@mediatek.com> (raw)
In-Reply-To: <CAD++jLmDKxCwSWZbKcpawjRotMgEFxaoCjcKiq8H87A39tnQqA@mail.gmail.com>
On Sat, 2026-07-25 at 15:10 +0200, Linus Walleij wrote:
> On Sat, Jul 25, 2026 at 3:02 PM Linus Walleij <linusw@kernel.org>
> wrote:
>
> > All patches applied, I had to rebase patch 5/5, please check the
> > result!
>
> Notably I had to add some lines for MT6858.
>
> Yours,
> Linus Walleij
Thanks for picking up the series, and for covering MT6858 in the
rebase.
I went over your MT6858 additions: the Kconfig entry matches the other
PARIS-based ones, and MODULE_LICENSE()/MODULE_DESCRIPTION()/
MODULE_DEVICE_TABLE() are all in place. No MODULE_IMPORT_NS() is needed
there - pinctrl-paris.c exports its entry points without a namespace,
and mt6858 references no namespaced symbol, same as the other 13
PARIS-based drivers.
Build-tested devel with arm64 allmodconfig (CONFIG_PINCTRL_MT6858=m):
drivers/pinctrl/mediatek/ builds warning-free, and modpost is happy -
no missing-licence or namespace complaints, and the OF aliases for
mt6858 are generated as expected.
One trivial nit, in case you rebase devel again: the attribution line
in
5/5 reads
[linusw@kernel.org: Rebased and added MT6858}
with a closing brace instead of a bracket.
Thanks,
Justin
prev parent reply other threads:[~2026-07-27 5:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 3:58 [PATCH v7 0/5] pinctrl: mediatek: Enable module build support Justin Yeh
2026-07-23 3:58 ` [PATCH v7 1/5] pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip Justin Yeh
2026-07-23 3:58 ` [PATCH v7 2/5] pinctrl: mediatek: free EINT resources on unbind Justin Yeh
2026-07-23 3:58 ` [PATCH v7 3/5] pinctrl: mediatek: allow common drivers to be built as modules Justin Yeh
2026-07-24 12:24 ` AngeloGioacchino Del Regno
2026-07-23 3:58 ` [PATCH v7 4/5] pinctrl: mediatek: mt7986: register both platform drivers from a single initcall Justin Yeh
2026-07-24 12:24 ` AngeloGioacchino Del Regno
2026-07-23 3:58 ` [PATCH v7 5/5] pinctrl: mediatek: enable module build support for all SoC drivers Justin Yeh
2026-07-25 13:02 ` [PATCH v7 0/5] pinctrl: mediatek: Enable module build support Linus Walleij
2026-07-25 13:10 ` Linus Walleij
2026-07-27 5:08 ` Justin Yeh (葉英茂) [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=9ca0e2e8a27262aa2c60b10b1ceec6b40a5dfa7c.camel@mediatek.com \
--to=justin.yeh@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linusw@kernel.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