From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Cc: Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
grom@black.igk.intel.com,
07110bfd5785d3bff71cebd710db42d6f5c4a643@black.igk.intel.com,
Mon@black.igk.intel.com, Sep@black.igk.intel.com,
17@black.igk.intel.com, "00:00:00"@black.igk.intel.com,
2001@black.igk.intel.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Tue, 16 Sep 2025 14:29:49 +0200 [thread overview]
Message-ID: <20250916123048.3058824-1-andriy.shevchenko@linux.intel.com> (raw)
clang is not happy about set but unused variable:
kernel/kexec_core.c:745:16: error: variable 'maddr' set but not used [-Werror,-Wunused-but-set-variable]
745 | unsigned long maddr;
| ^
1 error generated.
Fix the compilation breakage (`make W=1` build) by removing unused variable.
As Nathan noted, GCC 16 produces the similar warning;
Fixes: f4fecb50d6e1 ("kexec_core: remove superfluous page offset handling in segment loading")
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
v2: fixed Fixes (Nathan), added a note about GCC (Nathan), added tag (Nathan)
kernel/kexec_core.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
index 5357ed39e9d1..32722926bc7e 100644
--- a/kernel/kexec_core.c
+++ b/kernel/kexec_core.c
@@ -742,7 +742,6 @@ static int kimage_load_cma_segment(struct kimage *image, int idx)
struct kexec_segment *segment = &image->segment[idx];
struct page *cma = image->segment_cma[idx];
char *ptr = page_address(cma);
- unsigned long maddr;
size_t ubytes, mbytes;
int result = 0;
unsigned char __user *buf = NULL;
@@ -754,7 +753,6 @@ static int kimage_load_cma_segment(struct kimage *image, int idx)
buf = segment->buf;
ubytes = segment->bufsz;
mbytes = segment->memsz;
- maddr = segment->mem;
/* Then copy from source buffer to the CMA one */
while (mbytes) {
@@ -782,7 +780,6 @@ static int kimage_load_cma_segment(struct kimage *image, int idx)
}
ptr += mchunk;
- maddr += mchunk;
mbytes -= mchunk;
cond_resched();
--
2.50.1
next reply other threads:[~2025-09-16 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 12:29 Andy Shevchenko [this message]
2025-09-16 12:50 ` From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2024-08-19 18:45 Andy Shevchenko
2024-08-19 20:27 ` Andi Shyti
2024-08-21 14:11 ` Andi Shyti
2024-08-21 14:15 ` Andy Shevchenko
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=20250916123048.3058824-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc="00:00:00"@black.igk.intel.com \
--cc=07110bfd5785d3bff71cebd710db42d6f5c4a643@black.igk.intel.com \
--cc=17@black.igk.intel.com \
--cc=2001@black.igk.intel.com \
--cc=Mon@black.igk.intel.com \
--cc=Sep@black.igk.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=grom@black.igk.intel.com \
--cc=justinstitt@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
/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