From: Changwoo Min <changwoo@igalia.com>
To: lukasz.luba@arm.com, rafael@kernel.org, len.brown@intel.com,
pavel@kernel.org
Cc: christian.loehle@arm.com, tj@kernel.org, kernel-dev@igalia.com,
linux-pm@vger.kernel.org, sched-ext@lists.linux.dev,
linux-kernel@vger.kernel.org, Changwoo Min <changwoo@igalia.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH 1/2] PM: EM: Remove an unused variable in em_notify_pd_deleted()
Date: Mon, 20 Oct 2025 17:44:28 +0900 [thread overview]
Message-ID: <20251020084429.230322-1-changwoo@igalia.com> (raw)
The variable `ret` in em_notify_pd_deleted() is set but not used, so
that it causes the following warning:
>> kernel/power/em_netlink.c:228:6: warning: variable 'ret' set but
not used [-Wunused-but-set-variable]
So, let's remove the unused `ret` to avoid the warning.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202510151223.THlBK6QR-lkp@intel.com/
Signed-off-by: Changwoo Min <changwoo@igalia.com>
---
kernel/power/em_netlink.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/power/em_netlink.c b/kernel/power/em_netlink.c
index 2c55c758de6b..48752189a07b 100644
--- a/kernel/power/em_netlink.c
+++ b/kernel/power/em_netlink.c
@@ -269,7 +269,6 @@ static int __em_notify_pd_deleted_size(const struct em_perf_domain *pd)
void em_notify_pd_deleted(const struct em_perf_domain *pd)
{
struct sk_buff *msg;
- int ret = -EMSGSIZE;
void *hdr;
int msg_sz;
@@ -287,7 +286,6 @@ void em_notify_pd_deleted(const struct em_perf_domain *pd)
goto out_free_msg;
if (nla_put_u32(msg, EM_A_PD_TABLE_PD_ID, pd->id)) {
- ret = -EMSGSIZE;
goto out_free_msg;
}
--
2.51.1.dirty
next reply other threads:[~2025-10-20 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 8:44 Changwoo Min [this message]
2025-10-20 8:44 ` [PATCH 2/2] PM: EM: Include the iterator/accessor code for the performance domain conditionally Changwoo Min
2025-10-20 12:17 ` [PATCH 1/2] PM: EM: Remove an unused variable in em_notify_pd_deleted() Rafael J. Wysocki
2025-10-20 21:27 ` Changwoo Min
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=20251020084429.230322-1-changwoo@igalia.com \
--to=changwoo@igalia.com \
--cc=christian.loehle@arm.com \
--cc=kernel-dev@igalia.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lukasz.luba@arm.com \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®