From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216140] rtsx_usb causes error: xhci_hcd rejecting DMA map of vmalloc memory
Date: Wed, 13 Jul 2022 15:24:39 +0000 [thread overview]
Message-ID: <bug-216140-208809-bExEkoPH1a@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216140-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216140
Dimitar Kosev (buboleck@abv.bg) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |PATCH_ALREADY_AVAILABLE
--- Comment #4 from Dimitar Kosev (buboleck@abv.bg) ---
Fixed in 5.18.11/5.19-rc6 and later with commit
eb7f8e28420372787933eec079735c35034bda7d
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-07-13 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 11:20 [Bug 216140] New: rtsx_usb causes error: xhci_hcd rejecting DMA map of vmalloc memory bugzilla-daemon
2022-06-20 10:44 ` [Bug 216140] " bugzilla-daemon
2022-06-27 23:02 ` bugzilla-daemon
2022-06-28 11:29 ` bugzilla-daemon
2022-07-13 15:24 ` bugzilla-daemon [this message]
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-216140-208809-bExEkoPH1a@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.