From: sashiko-bot@kernel.org
To: "Petr Pavlu" <petr.pavlu@suse.com>
Cc: linux-watchdog@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-serial@vger.kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-modules@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH 1/3] watchdog: Replace __MODULE_STRING() with __stringify()
Date: Tue, 22 Sep 2026 13:41:53 +0000 [thread overview]
Message-ID: <20260922134154.040F81F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260922-module-string-v1-1-c18766690185@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
>
> Replace the remaining uses of __MODULE_STRING() with __stringify() in
> preparation for its removal.
>
> Link: https://git.kernel.org/tglx/history/c/136839a1b4 [1]
> 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/20260922-module-string-v1-0-c18766690185@suse.com?part=1
next prev parent reply other threads:[~2026-09-22 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 13:32 [PATCH 0/3] Remove obsolete __MODULE_STRING() Petr Pavlu
2026-09-22 13:32 ` [PATCH 1/3] watchdog: Replace __MODULE_STRING() with __stringify() Petr Pavlu
2026-09-22 13:41 ` sashiko-bot [this message]
2026-09-22 14:45 ` Wolfram Sang
2026-09-22 17:19 ` Guenter Roeck
2026-09-22 13:32 ` [PATCH 2/3] drivers: " Petr Pavlu
2026-09-22 13:41 ` sashiko-bot
2026-09-22 17:21 ` Guenter Roeck
2026-09-24 12:41 ` Petr Pavlu
2026-09-23 9:39 ` Greg Kroah-Hartman
2026-09-28 10:05 ` Andi Shyti
2026-09-28 16:18 ` Ian Abbott
2026-09-30 14:38 ` Alexandre Belloni
2026-09-22 13:32 ` [PATCH 3/3] module: Remove obsolete __MODULE_STRING() Petr Pavlu
2026-09-22 13:41 ` sashiko-bot
2026-09-22 17:44 ` Aaron Tomlin
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=20260922134154.040F81F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=dri-devel@lists.freedesktop.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.