All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Mathias Nyman <mathias.nyman@intel.com>,
	linux-usb@vger.kernel.org,
	Jonathan Bell <jonathan@raspberrypi.org>
Subject: Re: [PATCH] xhci: add quirk for host controllers that don't update endpoint DCS
Date: Fri, 02 Jul 2021 11:10:17 +0200	[thread overview]
Message-ID: <87h7hdf5dy.fsf@miraculix.mork.no> (raw)
In-Reply-To: <202107021602.N49dsX2f-lkp@intel.com> (kernel test robot's message of "Fri, 2 Jul 2021 16:57:33 +0800")

kernel test robot <lkp@intel.com> writes:

> All errors (new ones prefixed by >>):
>
>    drivers/usb/host/xhci-ring.c: In function 'xhci_move_dequeue_past_td':
>>> drivers/usb/host/xhci-ring.c:613:32: error: 'cur_td' undeclared (first use in this function)
>      613 |   halted_seg = trb_in_td(xhci, cur_td->start_seg,
>          |                                ^~~~~~
>    drivers/usb/host/xhci-ring.c:613:32: note: each undeclared identifier is reported only once for each function it appears in
>>> drivers/usb/host/xhci-ring.c:620:3: error: 'state' undeclared (first use in this function); did you mean 'statx'?
>      620 |   state->new_cycle_state = halted_trb->generic.field[3] & 0x1;
>          |   ^~~~~
>          |   statx

Ouch.  Sorry, this is embarrassing.  What you get for testing on stable
kernels and submitting to master.

Please ignore this patch. Will fix.



Bjørn

  reply	other threads:[~2021-07-02  9:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  7:13 [PATCH] xhci: add quirk for host controllers that don't update endpoint DCS Bjørn Mork
2021-07-02  8:57 ` kernel test robot
2021-07-02  8:57   ` kernel test robot
2021-07-02  9:10   ` Bjørn Mork [this message]
2021-07-20 15:09     ` [PATCH v2] " Bjørn Mork
2021-07-20 16:43       ` Rik van Riel
2021-09-01 15:30     ` [PATCH v2 RESEND] " Bjørn Mork
2021-09-27 18:30       ` Bjørn Mork
2021-09-29 14:24         ` Mathias Nyman
2021-07-02 12:21 ` [PATCH] " kernel test robot
2021-07-02 12:21   ` kernel test robot

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=87h7hdf5dy.fsf@miraculix.mork.no \
    --to=bjorn@mork.no \
    --cc=jonathan@raspberrypi.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.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.