From: Daniel Gomez <da.gomez@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Petr Pavlu" <petr.pavlu@suse.com>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Daniel Gomez" <da.gomez@samsung.com>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"David Gow" <davidgow@google.com>, "Rae Moar" <rmoar@google.com>
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Subject: Re: [PATCH 1/3] module: move 'struct module_use' to internal.h
Date: Thu, 19 Jun 2025 18:27:18 +0200 [thread overview]
Message-ID: <c5e3b6fc-e9dc-4551-b632-25dd2db9ec08@kernel.org> (raw)
In-Reply-To: <20250612-kunit-ifdef-modules-v1-1-fdccd42dcff8@linutronix.de>
On 12/06/2025 16.53, Thomas WeiÃschuh wrote:
> The struct was moved to the public header file in
> commit c8e21ced08b3 ("module: fix kdb's illicit use of struct module_use.").
> Back then the structure was used outside of the module core.
> Nowadays this is not true anymore, so the structure can be made internal.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Reviewed-by: Daniel Gomez <da.gomez@samsung.com>
next prev parent reply other threads:[~2025-06-19 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 14:53 [PATCH 0/3] module: make structure definitions always visible Thomas Weißschuh
2025-06-12 14:53 ` [PATCH 1/3] module: move 'struct module_use' to internal.h Thomas Weißschuh
2025-06-17 7:38 ` Petr Pavlu
2025-06-19 16:27 ` Daniel Gomez [this message]
2025-06-12 14:53 ` [PATCH 2/3] module: make structure definitions always visible Thomas Weißschuh
2025-07-07 19:11 ` Daniel Gomez
2025-07-08 9:32 ` Petr Pavlu
2025-07-11 6:29 ` Thomas Weißschuh
2025-07-11 13:24 ` Daniel Gomez
2025-07-08 9:39 ` Petr Pavlu
2025-06-12 14:53 ` [PATCH 3/3] kunit: test: Drop CONFIG_MODULE ifdeffery Thomas Weißschuh
2025-06-17 7:44 ` Petr Pavlu
2025-06-17 8:39 ` Thomas Weißschuh
2025-06-17 15:07 ` Petr Pavlu
2025-06-20 9:51 ` David Gow
2025-07-11 13:25 ` Daniel Gomez
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=c5e3b6fc-e9dc-4551-b632-25dd2db9ec08@kernel.org \
--to=da.gomez@kernel.org \
--cc=brendan.higgins@linux.dev \
--cc=da.gomez@samsung.com \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rmoar@google.com \
--cc=samitolvanen@google.com \
--cc=thomas.weissschuh@linutronix.de \
/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.