From: Mark Rutland <mark.rutland@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Vladimir Murzin <vladimir.murzin@arm.com>,
paulmck@kernel.org
Cc: Chunfeng Yun <chunfeng.yun@mediatek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG/PATCH] drivers/usb/mtu3: Work around mtu3_log_ep double-indirection issue
Date: Mon, 21 Sep 2026 15:00:45 +0100 [thread overview]
Message-ID: <arE4jcn4dCD9gos_@J2N7QTR9R3.cambridge.arm.com> (raw)
In-Reply-To: <20260909093524.249c2a1a@gandalf.local.home>
On Wed, Sep 09, 2026 at 09:35:24AM -0400, Steven Rostedt wrote:
> On Wed, 9 Sep 2026 11:31:28 +0100
> Vladimir Murzin <vladimir.murzin@arm.com> wrote:
>
> > I've done a little bit massaging and here is what worked for me
> >
> >
> > diff --git a/drivers/usb/mtu3/mtu3_trace.h b/drivers/usb/mtu3/mtu3_trace.h
> > index 89870175d635..4d4bae25fa1f 100644
> > --- a/drivers/usb/mtu3/mtu3_trace.h
> > +++ b/drivers/usb/mtu3/mtu3_trace.h
> > @@ -224,6 +224,7 @@ DECLARE_EVENT_CLASS(mtu3_log_ep,
> > __field(unsigned int, flags)
> > __field(unsigned int, direction)
> > __field(struct mtu3_gpd_ring *, gpd_ring)
> > + __field(dma_addr_t, gpd_ring_dma)
> > ),
> > TP_fast_assign(
> > __assign_str(name);
> > @@ -235,12 +236,13 @@ DECLARE_EVENT_CLASS(mtu3_log_ep,
> > __entry->flags = mep->flags;
> > __entry->direction = mep->is_in;
> > __entry->gpd_ring = &mep->gpd_ring;
> > + __entry->gpd_ring_dma = mep->gpd_ring.dma;
> > ),
> > TP_printk("%s: type %s maxp %d slot %d mult %d burst %d ring %p/%pad flags %c:%c%c%c:%c",
> > __get_str(name), usb_ep_type_string(__entry->type),
> > __entry->maxp, __entry->slot,
> > __entry->mult, __entry->maxburst,
> > - __entry->gpd_ring, &__entry->gpd_ring->dma,
> > + __entry->gpd_ring, &__entry->gpd_ring_dma,
> > __entry->flags & MTU3_EP_ENABLED ? 'E' : 'e',
> > __entry->flags & MTU3_EP_STALL ? 'S' : 's',
> > __entry->flags & MTU3_EP_WEDGE ? 'W' : 'w',
>
> LGTM,
>
> Reviewed-by: Steven Rostedt <rostedt@goodmis.org>
On v7.3-rc4 I still see the splat Paul reported initially, and the above
fixes that, so FWIW:
Tested-by: Mark Rutland <mark.rutland@arm.com>
Steve, I assume you were expecting someone to send the above as a full
patch.
Paul, do you intend to send a v2, or should Vladimir send out his
version as its own patch? I assume you're happy with a Reported-by, if
he does that?
Mark.
next prev parent reply other threads:[~2026-09-21 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 23:59 Paul E. McKenney
2026-09-07 13:28 ` Vladimir Murzin
2026-09-08 18:08 ` Paul E. McKenney
2026-09-09 10:31 ` Vladimir Murzin
2026-09-09 13:35 ` Steven Rostedt
2026-09-21 14:00 ` Mark Rutland [this message]
2026-09-21 14:08 ` Steven Rostedt
2026-09-21 16:14 ` Paul E. McKenney
2026-09-22 10:40 ` Vladimir Murzin
2026-09-09 13:34 ` Steven Rostedt
2026-09-09 15:14 ` Paul E. McKenney
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=arE4jcn4dCD9gos_@J2N7QTR9R3.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=chunfeng.yun@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=vladimir.murzin@arm.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
all inboxes | Powered by JetHome®