From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Hector Martin 'marcan'" <marcan@marcan.st>
Cc: Clemens Ladisch <clemens@ladisch.de>,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire-ohci: work around oversized DMA reads on JMicron controllers
Date: Sat, 13 Jan 2018 17:55:23 +0100 [thread overview]
Message-ID: <20180113175523.06420aec@kant> (raw)
In-Reply-To: <5ec332fc-136d-11cc-fc0d-e95a00d6b133@marcan.st>
On Jan 11 Hector Martin 'marcan' wrote:
> On 2017-11-13 06:05, Stefan Richter wrote:
> > Thanks Hector for the troubleshooting and for the patch.
> > Thanks Clemens for the review.
> >
> > It's been a while since I last reviewed and tested kernel patches, and
> > also my main FireWire equipped PC is currently tied up in work for which
> > reboots aren't desirable. But I am updating a long unused secondary
> > FireWire'd PC right now and give the patch some testing this week. (This
> > one even has a JMicron controller, but not an IOMMU.)
> >
> Hi Stefan, did you ever get around to testing the patch? It doesn't seem
> to have made it into any trees or percolated up to mainline yet.
Pushed to linux1394.git:for-next now. Sorry that I took so long.
Thanks once more for your effort.
(Getting the test computer up to date was a PITA; no fun when there is
almost no spare time...)
--
Stefan Richter
-======---=- ---= -==-=
http://arcgraph.de/sr/
prev parent reply other threads:[~2018-01-13 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 11:28 [PATCH] firewire-ohci: work around oversized DMA reads on JMicron controllers Hector Martin
2017-11-03 14:21 ` Clemens Ladisch
2017-11-12 21:05 ` Stefan Richter
2018-01-11 2:31 ` Hector Martin 'marcan'
2018-01-13 16:55 ` Stefan Richter [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=20180113175523.06420aec@kant \
--to=stefanr@s5r6.in-berlin.de \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=marcan@marcan.st \
/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