From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Udipto Goswami <quic_ugoswami@quicinc.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@intel.com>
Cc: Pratham Pratap <quic_ppratap@quicinc.com>,
Jack Pham <quic_jackp@quicinc.com>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: xhci: Remove unused udev from xhci_log_ctx trace event
Date: Thu, 23 Mar 2023 16:15:29 +0200 [thread overview]
Message-ID: <6edd8939-062a-9548-893b-8f02598c2fec@linux.intel.com> (raw)
In-Reply-To: <20230323131315.21764-1-quic_ugoswami@quicinc.com>
On 23.3.2023 15.13, Udipto Goswami wrote:
> xhci_log_ctx event is not utilizing the extracted udev to
> print out anything, hence removing it.
>
> Fixes: 1d27fabec068 ("xhci: add xhci_address_ctx trace event")
> Signed-off-by: Udipto Goswami <quic_ugoswami@quicinc.com>
> ---
> drivers/usb/host/xhci-trace.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/usb/host/xhci-trace.h b/drivers/usb/host/xhci-trace.h
> index 4286dba5b157..7555c4ea7c4b 100644
> --- a/drivers/usb/host/xhci-trace.h
> +++ b/drivers/usb/host/xhci-trace.h
> @@ -80,20 +80,16 @@ DECLARE_EVENT_CLASS(xhci_log_ctx,
> __field(dma_addr_t, ctx_dma)
> __field(u8 *, ctx_va)
> __field(unsigned, ctx_ep_num)
> - __field(int, slot_id)
> __dynamic_array(u32, ctx_data,
> ((HCC_64BYTE_CONTEXT(xhci->hcc_params) + 1) * 8) *
> ((ctx->type == XHCI_CTX_TYPE_INPUT) + ep_num + 1))
> ),
> TP_fast_assign(
> - struct usb_device *udev;
>
> - udev = to_usb_device(xhci_to_hcd(xhci)->self.controller);
Looks like this was flawed from the beginning, forcing a device struct for a host controller into
a struct usb_device
Adding to queue
Thanks
Mathias
next prev parent reply other threads:[~2023-03-23 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 13:13 [PATCH] usb: xhci: Remove unused udev from xhci_log_ctx trace event Udipto Goswami
2023-03-23 14:15 ` Mathias Nyman [this message]
2023-05-09 5:10 ` Udipto Goswami
2023-05-09 8:06 ` Mathias Nyman
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=6edd8939-062a-9548-893b-8f02598c2fec@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=quic_jackp@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=quic_ugoswami@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.