From: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com>
To: linusw@kernel.org, brgl@kernel.org
Cc: andriy.shevchenko@intel.com, dev-jorge.sanjuangarcia@duagon.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jose Javier Rodriguez Barbarin
<dev-josejavier.rodriguez@duagon.com>
Subject: [PATCH v2 1/1] gpio: gpio-menz127: drop unneeded MODULE_ALIAS
Date: Thu, 8 Jan 2026 14:48:43 +0100 [thread overview]
Message-ID: <20260108134843.25903-2-dev-josejavier.rodriguez@duagon.com> (raw)
In-Reply-To: <20260108134843.25903-1-dev-josejavier.rodriguez@duagon.com>
Since commit 1f4ea4838b13 ("mcb: Add missing modpost build support")
the MODULE_ALIAS() is redundant as the module alias is now
automatically generated from the MODULE_DEVICE_TABLE().
Remove the explicit alias.
No functional change intended.
Reviewed-by: Jorge Sanjuan Garcia <dev-jorge.sanjuangarcia@duagon.com>
Signed-off-by: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com>
---
drivers/gpio/gpio-menz127.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpio/gpio-menz127.c b/drivers/gpio/gpio-menz127.c
index 52b13c6ae496..f51e7517f551 100644
--- a/drivers/gpio/gpio-menz127.c
+++ b/drivers/gpio/gpio-menz127.c
@@ -223,5 +223,4 @@ module_mcb_driver(men_z127_driver);
MODULE_AUTHOR("Andreas Werner <andreas.werner@men.de>");
MODULE_DESCRIPTION("MEN GPIO Controller");
MODULE_LICENSE("GPL v2");
-MODULE_ALIAS("mcb:16z127");
MODULE_IMPORT_NS("MCB");
--
2.52.0
next prev parent reply other threads:[~2026-01-08 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 13:48 [PATCH v2 0/1] gpio: Remove MODULE_ALIAS from gpio-menz127 Jose Javier Rodriguez Barbarin
2026-01-08 13:48 ` Jose Javier Rodriguez Barbarin [this message]
2026-01-09 8:31 ` [PATCH v2 1/1] gpio: gpio-menz127: drop unneeded MODULE_ALIAS Bartosz Golaszewski
2026-01-09 11:30 ` Jose Javier Rodriguez Barbarin
2026-01-12 10:40 ` [PATCH v2 0/1] gpio: Remove MODULE_ALIAS from gpio-menz127 Bartosz Golaszewski
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=20260108134843.25903-2-dev-josejavier.rodriguez@duagon.com \
--to=dev-josejavier.rodriguez@duagon.com \
--cc=andriy.shevchenko@intel.com \
--cc=brgl@kernel.org \
--cc=dev-jorge.sanjuangarcia@duagon.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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