From: kernel test robot <lkp@intel.com>
To: Jill Donahue <jilliandonahue58@gmail.com>,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jill Donahue <jilliandonahue58@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] f_midi_complete to call tasklet_hi_schedule
Date: Sat, 8 Feb 2025 20:42:17 +0800 [thread overview]
Message-ID: <202502082022.ILQXjseT-lkp@intel.com> (raw)
In-Reply-To: <20250207203441.945196-1-jilliandonahue58@gmail.com>
Hi Jill,
kernel test robot noticed the following build errors:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on usb/usb-next usb/usb-linus westeri-thunderbolt/next linus/master v6.14-rc1 next-20250207]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jill-Donahue/f_midi_complete-to-call-tasklet_hi_schedule/20250208-043845
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
patch link: https://lore.kernel.org/r/20250207203441.945196-1-jilliandonahue58%40gmail.com
patch subject: [PATCH v3] f_midi_complete to call tasklet_hi_schedule
config: arm-randconfig-002-20250208 (https://download.01.org/0day-ci/archive/20250208/202502082022.ILQXjseT-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250208/202502082022.ILQXjseT-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/202502082022.ILQXjseT-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/usb/gadget/function/f_midi.c:286:31: error: no member named 'tasklet' in 'struct f_midi'
286 | tasklet_hi_schedule(&midi->tasklet);
| ~~~~ ^
1 error generated.
vim +286 drivers/usb/gadget/function/f_midi.c
269
270 static void
271 f_midi_complete(struct usb_ep *ep, struct usb_request *req)
272 {
273 struct f_midi *midi = ep->driver_data;
274 struct usb_composite_dev *cdev = midi->func.config->cdev;
275 int status = req->status;
276
277 switch (status) {
278 case 0: /* normal completion */
279 if (ep == midi->out_ep) {
280 /* We received stuff. req is queued again, below */
281 f_midi_handle_out_data(ep, req);
282 } else if (ep == midi->in_ep) {
283 /* Our transmit completed. See if there's more to go.
284 * f_midi_transmit eats req, don't queue it again. */
285 req->length = 0;
> 286 tasklet_hi_schedule(&midi->tasklet);
287 return;
288 }
289 break;
290
291 /* this endpoint is normally active while we're configured */
292 case -ECONNABORTED: /* hardware forced ep reset */
293 case -ECONNRESET: /* request dequeued */
294 case -ESHUTDOWN: /* disconnect from host */
295 VDBG(cdev, "%s gone (%d), %d/%d\n", ep->name, status,
296 req->actual, req->length);
297 if (ep == midi->out_ep) {
298 f_midi_handle_out_data(ep, req);
299 /* We don't need to free IN requests because it's handled
300 * by the midi->in_req_fifo. */
301 free_ep_req(ep, req);
302 }
303 return;
304
305 case -EOVERFLOW: /* buffer overrun on read means that
306 * we didn't provide a big enough buffer.
307 */
308 default:
309 DBG(cdev, "%s complete --> %d, %d/%d\n", ep->name,
310 status, req->actual, req->length);
311 break;
312 case -EREMOTEIO: /* short read */
313 break;
314 }
315
316 status = usb_ep_queue(ep, req, GFP_ATOMIC);
317 if (status) {
318 ERROR(cdev, "kill %s: resubmit %d bytes --> %d\n",
319 ep->name, req->length, status);
320 usb_ep_set_halt(ep);
321 /* FIXME recover later ... somehow */
322 }
323 }
324
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-08 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 20:34 [PATCH v3] f_midi_complete to call tasklet_hi_schedule Jill Donahue
2025-02-08 7:14 ` Greg KH
2025-02-08 12:10 ` kernel test robot
2025-02-08 12:42 ` kernel test robot [this message]
2025-02-10 17:18 ` Jillian Donahue
2025-02-11 5:59 ` Greg KH
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=202502082022.ILQXjseT-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jilliandonahue58@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stable@vger.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