From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: Dmitry Osipenko <digetx@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Peter Chen <peter.chen@kernel.org>,
Peter Geis <pgwipeout@gmail.com>,
Thierry Reding <treding@nvidia.com>
Cc: linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [PATCH 0/3] usb: chipidea: Tegra USB DMA fix + cleanups
Date: Sat, 23 Sep 2023 21:41:52 +0200 [thread overview]
Message-ID: <cover.1695497666.git.mirq-linux@rere.qmqm.pl> (raw)
This series contains a fix for a DMA buffer overflow in Tegra USB driver
followed by a cleanup of the DMA bounce buffer code and another cleanup
to make probe() consistently use dev_err_probe() for error printk()s.
Michał Mirosław (3):
usb: chipidea: Fix DMA overwrite for Tegra
usb: chipidea: Simplify Tegra DMA alignment code
usb: chipidea: tegra: Consistently use dev_err_probe()
drivers/usb/chipidea/ci_hdrc_tegra.c | 16 ++++------
drivers/usb/chipidea/host.c | 48 ++++++++++++----------------
2 files changed, 27 insertions(+), 37 deletions(-)
--
2.39.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-09-23 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 19:41 Michał Mirosław [this message]
2023-09-23 19:41 ` [PATCH 1/3] usb: chipidea: Fix DMA overwrite for Tegra Michał Mirosław
2023-09-25 11:45 ` Peter Chen
2023-09-25 23:53 ` Michał Mirosław
2023-09-26 12:11 ` Peter Chen
2023-09-23 19:41 ` [PATCH 2/3] usb: chipidea: Simplify Tegra DMA alignment code Michał Mirosław
2023-09-23 19:41 ` [PATCH 3/3] usb: chipidea: tegra: Consistently use dev_err_probe() Michał Mirosław
2023-09-25 11:47 ` Peter Chen
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.1695497666.git.mirq-linux@rere.qmqm.pl \
--to=mirq-linux@rere.qmqm.pl \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=pgwipeout@gmail.com \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).