From: sashiko-bot@kernel.org
To: "Petr Pavlu" <petr.pavlu@suse.com>
Cc: "Petr Pavlu" <petr.pavlu@suse.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org, linux-serial@vger.kernel.org,
linux-hwmon@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-wired-lan@lists.osuosl.org, linux-modules@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 3/3] module: Remove obsolete __MODULE_STRING()
Date: Fri, 02 Oct 2026 09:14:48 +0000 [thread overview]
Message-ID: <20261002091448.DB0911F00893@smtp.kernel.org> (raw)
In-Reply-To: <20261002-module-string-v2-3-fc7438acaf4d@suse.com>
> __MODULE_STRING() has been an alias for __stringify() since "[PATCH]
> MODULE_PARM support for older modules" [1] in 2002-12. That change also
> moved it to the graveyard section at the end of linux/module.h
>
> Remove __MODULE_STRING() now that all remaining uses have been replaced
> directly with __stringify().
>
> Link: https://git.kernel.org/tglx/history/c/136839a1b4 [1]
> Reviewed-by: Aaron Tomlin <atomlin@atomlin.com>
> Signed-off-by: Petr Pavlu <petr.pavlu@suse.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261002-module-string-v2-0-fc7438acaf4d@suse.com?part=3
prev parent reply other threads:[~2026-10-02 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 8:31 [PATCH v2 0/3] Remove obsolete __MODULE_STRING() Petr Pavlu
2026-10-02 8:31 ` [PATCH v2 1/3] hwmon: Replace __MODULE_STRING() with __stringify() Petr Pavlu
2026-10-02 9:14 ` sashiko-bot
2026-10-02 14:04 ` Loktionov, Aleksandr
2026-10-02 8:31 ` [PATCH v2 2/3] drivers: " Petr Pavlu
2026-10-02 8:49 ` Mika Westerberg
2026-10-02 9:14 ` sashiko-bot
2026-10-02 14:05 ` Loktionov, Aleksandr
2026-10-02 8:31 ` [PATCH v2 3/3] module: Remove obsolete __MODULE_STRING() Petr Pavlu
2026-10-02 9:14 ` sashiko-bot [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=20261002091448.DB0911F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=petr.pavlu@suse.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.