From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215890] Regression in 5.18: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory
Date: Sun, 15 May 2022 21:38:41 +0000 [thread overview]
Message-ID: <bug-215890-208809-bRodmT0aiB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215890-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215890
--- Comment #15 from Satadru Pramanik (satadru@umich.edu) ---
(In reply to Mathias Nyman from comment #12)
> Created attachment 300952 [details]
> bcm5974_add_urb_flag
>
> quick testpatch that just adds the missing URB flags,
> Does it work? I don't have this hardware myself
Could we get that patch added to the driver for 5.18?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-05-15 21:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 22:42 [Bug 215890] New: Regression in 5.18: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory bugzilla-daemon
2022-05-02 14:19 ` [Bug 215890] " bugzilla-daemon
2022-05-04 8:42 ` [Bug 215890] New: " Thorsten Leemhuis
2022-05-13 8:24 ` Thorsten Leemhuis
2022-05-13 10:37 ` Christoph Hellwig
2022-05-13 10:47 ` Christoph Hellwig
2022-05-20 5:38 ` [Bug 215890] New: Regression in 5.18: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory #forregzbot Thorsten Leemhuis
2022-05-04 8:42 ` [Bug 215890] Regression in 5.18: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory bugzilla-daemon
2022-05-09 0:50 ` bugzilla-daemon
2022-05-10 8:48 ` bugzilla-daemon
2022-05-10 20:50 ` bugzilla-daemon
2022-05-11 5:44 ` Greg KH
2022-05-11 5:44 ` bugzilla-daemon
2022-05-12 16:36 ` bugzilla-daemon
2022-05-13 8:24 ` bugzilla-daemon
2022-05-13 10:37 ` bugzilla-daemon
2022-05-13 10:47 ` bugzilla-daemon
2022-05-13 13:21 ` bugzilla-daemon
2022-05-13 13:33 ` bugzilla-daemon
2022-05-13 13:50 ` bugzilla-daemon
2022-05-13 15:22 ` bugzilla-daemon
2022-05-15 21:38 ` bugzilla-daemon [this message]
2022-05-16 3:27 ` bugzilla-daemon
2022-05-16 10:23 ` bugzilla-daemon
2022-05-16 11:39 ` bugzilla-daemon
2022-05-16 12:16 ` bugzilla-daemon
2022-05-16 12:17 ` bugzilla-daemon
2022-05-18 7:48 ` bugzilla-daemon
2022-05-25 17:58 ` bugzilla-daemon
2022-06-03 13:45 ` bugzilla-daemon
2022-06-06 13:22 ` bugzilla-daemon
2022-06-16 10:38 ` bugzilla-daemon
2022-06-16 10:59 ` bugzilla-daemon
2022-06-16 11:21 ` bugzilla-daemon
2022-07-26 15:12 ` bugzilla-daemon
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=bug-215890-208809-bRodmT0aiB@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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 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.