public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Justin Yeh <justin.yeh@mediatek•com>
To: Sean Wang <sean.wang@kernel•org>,
	Linus Walleij <linusw@kernel•org>,
	Matthias Brugger <matthias.bgg@gmail•com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora•com>
Cc: <Project_Global_Chrome_Upstream_Group@mediatek•com>,
	<linux-mediatek@lists•infradead.org>,
	<linux-gpio@vger•kernel.org>, <linux-kernel@vger•kernel.org>,
	<linux-arm-kernel@lists•infradead.org>,
	Justin Yeh <justin.yeh@mediatek•com>
Subject: [PATCH 2/2] pinctrl: mediatek: mt8189: Add MODULE_LICENSE declaration
Date: Fri, 29 May 2026 18:02:42 +0800	[thread overview]
Message-ID: <20260529100308.51271-3-justin.yeh@mediatek.com> (raw)
In-Reply-To: <20260529100308.51271-1-justin.yeh@mediatek.com>

Add missing MODULE_LICENSE("GPL v2") macro to fix modpost error during
kernel module build. The license identifier matches the SPDX header
(GPL-2.0) at the top of the file.

This fixes the following build error:
  ERROR: modpost: missing MODULE_LICENSE() in pinctrl-mt8189.o

Signed-off-by: Justin Yeh <justin.yeh@mediatek•com>
---
 drivers/pinctrl/mediatek/pinctrl-mt8189.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/pinctrl/mediatek/pinctrl-mt8189.c b/drivers/pinctrl/mediatek/pinctrl-mt8189.c
index cd4cdff309a1..a9c128c514a4 100644
--- a/drivers/pinctrl/mediatek/pinctrl-mt8189.c
+++ b/drivers/pinctrl/mediatek/pinctrl-mt8189.c
@@ -1696,3 +1696,4 @@ static int __init mt8189_pinctrl_init(void)
 arch_initcall(mt8189_pinctrl_init);
 
 MODULE_DESCRIPTION("MediaTek MT8189 Pinctrl Driver");
+MODULE_LICENSE("GPL v2");
-- 
2.45.2



      parent reply	other threads:[~2026-05-29 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 10:02 [PATCH 0/2] pinctrl: mediatek: Enable MT8189 as loadable module Justin Yeh
2026-05-29 10:02 ` [PATCH 1/2] pinctrl: mediatek: Restore PINCTRL_MT8189 to tristate Justin Yeh
2026-05-29 10:02 ` 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=20260529100308.51271-3-justin.yeh@mediatek.com \
    --to=justin.yeh@mediatek$(echo .)com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek$(echo .)com \
    --cc=angelogioacchino.delregno@collabora$(echo .)com \
    --cc=linusw@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-gpio@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mediatek@lists$(echo .)infradead.org \
    --cc=matthias.bgg@gmail$(echo .)com \
    --cc=sean.wang@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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