From: kernel test robot <lkp@intel.com>
To: Mayuresh Chitale <mayuresh.chitale@oss.qualcomm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Anup Patel <anup@brainfault.org>
Subject: [avpatel:riscv_trace_support_v3 55/60] drivers/hwtracing/rvtrace/rvtrace-ramsink.c:114:23: warning: variable 'trram_ctrl' set but not used
Date: Mon, 16 Feb 2026 19:56:54 +0800 [thread overview]
Message-ID: <202602161901.2CFPiPwM-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_trace_support_v3
head: 42acf36a226e81d2e18eb340bbfd6d7ab09b8c1e
commit: 32999331eb99f67ab5abc1a7c8a62a8bf75ed0f2 [55/60] rvtrace: Add trace ramsink driver
config: riscv-randconfig-002-20260216 (https://download.01.org/0day-ci/archive/20260216/202602161901.2CFPiPwM-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project e86750b29fa0ff207cd43213d66dabe565417638)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260216/202602161901.2CFPiPwM-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202602161901.2CFPiPwM-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/hwtracing/rvtrace/rvtrace-ramsink.c:114:23: warning: variable 'trram_ctrl' set but not used [-Wunused-but-set-variable]
114 | u32 wp_low, wp_high, trram_ctrl;
| ^
1 warning generated.
vim +/trram_ctrl +114 drivers/hwtracing/rvtrace/rvtrace-ramsink.c
107
108 static size_t rvtrace_ramsink_copyto_auxbuf(struct rvtrace_component *comp,
109 struct rvtrace_perf_auxbuf *buf)
110 {
111 struct rvtrace_ramsink_priv *priv = dev_get_drvdata(&comp->dev);
112 size_t size_wp_end = 0, size_start_wp = 0;
113 struct trace_buf src, dst;
> 114 u32 wp_low, wp_high, trram_ctrl;
115 u64 buf_cur_head;
116
117 dst.base = buf->base;
118 dst.len = buf->length;
119 dst.cur = buf->pos;
120 src.base = priv->va;
121 src.len = priv->size;
122 wp_low = rvtrace_read32(comp->pdata, RVTRACE_RAMSINK_WPLOW_OFF);
123 wp_high = rvtrace_read32(comp->pdata, RVTRACE_RAMSINK_WPHIGH_OFF);
124 buf_cur_head = (u64)(wp_high) << 32 | wp_low;
125 trram_ctrl = rvtrace_read32(comp->pdata, RVTRACE_COMPONENT_CTRL_OFFSET);
126 if (buf_cur_head & 0x1) {
127 buf_cur_head &= ~RVTRACE_RAMSINK_WPLOW_WRAP;
128 rvtrace_write32(comp->pdata, lower_32_bits(priv->start),
129 RVTRACE_RAMSINK_WPLOW_OFF);
130 rvtrace_write32(comp->pdata, upper_32_bits(priv->start),
131 RVTRACE_RAMSINK_WPHIGH_OFF);
132 src.cur = buf_cur_head - priv->start;
133 size_wp_end = priv->end - buf_cur_head;
134 tbuf_to_pbuf_copy(&src, &dst, size_wp_end);
135 }
136
137 src.cur = 0;
138 size_start_wp = buf_cur_head - priv->start;
139 tbuf_to_pbuf_copy(&src, &dst, size_start_wp);
140 dev_dbg(&comp->dev, "Copied %zu bytes\n", size_wp_end + size_start_wp);
141 return (size_wp_end + size_start_wp);
142 }
143
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-16 11:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202602161901.2CFPiPwM-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=llvm@lists.linux.dev \
--cc=mayuresh.chitale@oss.qualcomm.com \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox