From: Shuah Khan <skhan@linuxfoundation.org>
To: arnd@arndb.de, gregkh@linuxfoundation.org
Cc: Shuah Khan <skhan@linuxfoundation.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] rtsx_usb fixes
Date: Thu, 30 Jun 2022 20:32:54 -0600 [thread overview]
Message-ID: <cover.1656642167.git.skhan@linuxfoundation.org> (raw)
This two patch series consists of:
-- fix to "rejecting DMA map of vmalloc memory" dma mapping error
due to passing dma mapped buffer to usb_bulk_msg(). This results
in an attempt to map it again and fail.
-- a second fix to use separate command and response buffers to avoid
potential conflicts.
Shuah Khan (2):
misc: rtsx_usb: fix use of dma mapped buffer for usb bulk transfer
misc: rtsx_usb: use separate command and response buffers
drivers/misc/cardreader/rtsx_usb.c | 25 +++++++++++++++++--------
include/linux/rtsx_usb.h | 2 --
2 files changed, 17 insertions(+), 10 deletions(-)
--
2.34.1
next reply other threads:[~2022-07-01 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 2:32 Shuah Khan [this message]
2022-07-01 2:32 ` [PATCH 1/2] misc: rtsx_usb: fix use of dma mapped buffer for usb bulk transfer Shuah Khan
2022-07-01 2:32 ` [PATCH 2/2] misc: rtsx_usb: use separate command and response buffers Shuah Khan
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=cover.1656642167.git.skhan@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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