All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Zhongjin <chenzhongjin@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-modules@vger.kernel.org>
Cc: <mcgrof@kernel.org>, <chenzhongjin@huawei.com>
Subject: [PATCH -next] module: Remove unused macros module_addr_min/max
Date: Sat, 24 Sep 2022 15:22:16 +0800	[thread overview]
Message-ID: <20220924072216.103876-1-chenzhongjin@huawei.com> (raw)

Unused macros reported by [-Wunused-macros].

These macros are introduced to record the bound address of modules.

'80b8bf436990 ("module: Always have struct mod_tree_root")'
This commit has made struct mod_tree_root always exist, which means
we can always referencing mod_tree derectly rather than using this
macro.

So they are useless, remove them for code cleaning.

Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
---
 kernel/module/main.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/kernel/module/main.c b/kernel/module/main.c
index a4e4d84b6f4e..96dcc950da60 100644
--- a/kernel/module/main.c
+++ b/kernel/module/main.c
@@ -84,9 +84,6 @@ struct mod_tree_root mod_data_tree __cacheline_aligned = {
 };
 #endif
 
-#define module_addr_min mod_tree.addr_min
-#define module_addr_max mod_tree.addr_max
-
 struct symsearch {
 	const struct kernel_symbol *start, *stop;
 	const s32 *crcs;
-- 
2.17.1


             reply	other threads:[~2022-09-24  7:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24  7:22 Chen Zhongjin [this message]
2022-09-26  5:50 ` [PATCH -next] module: Remove unused macros module_addr_min/max Christophe Leroy
2022-09-30 11:37 ` Miroslav Benes
2022-10-03 23:43   ` Luis Chamberlain

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=20220924072216.103876-1-chenzhongjin@huawei.com \
    --to=chenzhongjin@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@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 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.