From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:dev.2026.09.03a 43/55] drivers/usb/mtu3/./mtu3_trace.h:239:55: error: invalid type argument of '->' (have 'struct mtu3_gpd_ring')
Date: Thu, 10 Sep 2026 09:50:38 +0800 [thread overview]
Message-ID: <202609100921.vDOlHS7p-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2026.09.03a
head: 6c5c244f4b239bc4d284e58a2f79a143648557cb
commit: afda2321e6e93a5bcc28bfb4717fbc3a1768446c [43/55] EXP drivers/usb/mtu3: Work around mtu3_log_ep double-indirection issue
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20260910/202609100921.vDOlHS7p-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260910/202609100921.vDOlHS7p-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/202609100921.vDOlHS7p-lkp@intel.com/
Note: the paulmck-rcu/dev.2026.09.03a HEAD 6c5c244f4b239bc4d284e58a2f79a143648557cb builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
In file included from include/trace/define_trace.h:132,
from drivers/usb/mtu3/mtu3_trace.h:279,
from drivers/usb/mtu3/mtu3_trace.c:12:
drivers/usb/mtu3/./mtu3_trace.h: In function 'do_trace_event_raw_event_mtu3_log_ep':
>> drivers/usb/mtu3/./mtu3_trace.h:239:55: error: invalid type argument of '->' (have 'struct mtu3_gpd_ring')
239 | __entry->gpd_ring_dma = &mep->gpd_ring->dma;
| ^~
include/trace/trace_events.h:448:11: note: in definition of macro '__DECLARE_EVENT_CLASS'
448 | { assign; } \
| ^~~~~~
include/trace/trace_events.h:456:23: note: in expansion of macro 'PARAMS'
456 | PARAMS(assign), PARAMS(print)) \
| ^~~~~~
drivers/usb/mtu3/./mtu3_trace.h:214:1: note: in expansion of macro 'DECLARE_EVENT_CLASS'
214 | DECLARE_EVENT_CLASS(mtu3_log_ep,
| ^~~~~~~~~~~~~~~~~~~
drivers/usb/mtu3/./mtu3_trace.h:229:9: note: in expansion of macro 'TP_fast_assign'
229 | TP_fast_assign(
| ^~~~~~~~~~~~~~
In file included from include/trace/define_trace.h:133:
drivers/usb/mtu3/./mtu3_trace.h: In function 'do_perf_trace_mtu3_log_ep':
>> drivers/usb/mtu3/./mtu3_trace.h:239:55: error: invalid type argument of '->' (have 'struct mtu3_gpd_ring')
239 | __entry->gpd_ring_dma = &mep->gpd_ring->dma;
| ^~
include/trace/perf.h:51:11: note: in definition of macro '__DECLARE_EVENT_CLASS'
51 | { assign; } \
| ^~~~~~
include/trace/perf.h:67:23: note: in expansion of macro 'PARAMS'
67 | PARAMS(assign), PARAMS(print)) \
| ^~~~~~
drivers/usb/mtu3/./mtu3_trace.h:214:1: note: in expansion of macro 'DECLARE_EVENT_CLASS'
214 | DECLARE_EVENT_CLASS(mtu3_log_ep,
| ^~~~~~~~~~~~~~~~~~~
drivers/usb/mtu3/./mtu3_trace.h:229:9: note: in expansion of macro 'TP_fast_assign'
229 | TP_fast_assign(
| ^~~~~~~~~~~~~~
vim +239 drivers/usb/mtu3/./mtu3_trace.h
213
214 DECLARE_EVENT_CLASS(mtu3_log_ep,
215 TP_PROTO(struct mtu3_ep *mep),
216 TP_ARGS(mep),
217 TP_STRUCT__entry(
218 __string(name, mep->name)
219 __field(unsigned int, type)
220 __field(unsigned int, slot)
221 __field(unsigned int, maxp)
222 __field(unsigned int, mult)
223 __field(unsigned int, maxburst)
224 __field(unsigned int, flags)
225 __field(unsigned int, direction)
226 __field(struct mtu3_gpd_ring *, gpd_ring)
227 __field(dma_addr_t *, gpd_ring_dma)
228 ),
229 TP_fast_assign(
230 __assign_str(name);
231 __entry->type = mep->type;
232 __entry->slot = mep->slot;
233 __entry->maxp = mep->ep.maxpacket;
234 __entry->mult = mep->ep.mult;
235 __entry->maxburst = mep->ep.maxburst;
236 __entry->flags = mep->flags;
237 __entry->direction = mep->is_in;
238 __entry->gpd_ring = &mep->gpd_ring;
> 239 __entry->gpd_ring_dma = &mep->gpd_ring->dma;
240 ),
241 TP_printk("%s: type %s maxp %d slot %d mult %d burst %d ring %p/%pad flags %c:%c%c%c:%c",
242 __get_str(name), usb_ep_type_string(__entry->type),
243 __entry->maxp, __entry->slot,
244 __entry->mult, __entry->maxburst,
245 __entry->gpd_ring, __entry->gpd_ring_dma,
246 __entry->flags & MTU3_EP_ENABLED ? 'E' : 'e',
247 __entry->flags & MTU3_EP_STALL ? 'S' : 's',
248 __entry->flags & MTU3_EP_WEDGE ? 'W' : 'w',
249 __entry->flags & MTU3_EP_BUSY ? 'B' : 'b',
250 __entry->direction ? '<' : '>'
251 )
252 );
253
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-10 1:50 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=202609100921.vDOlHS7p-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@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®