From: Christoph Hellwig <hch@lst.de>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Christoph Hellwig <hch@lst.de>, "corbet@lwn.net" <corbet@lwn.net>,
"jroedel@suse.de" <jroedel@suse.de>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Subject: Re: [PATCH] Documentation: DMA-API: fix a function name of max_mapping_size
Date: Fri, 7 Jun 2019 10:34:47 +0200 [thread overview]
Message-ID: <20190607083447.GA10860@lst.de> (raw)
In-Reply-To: <TYAPR01MB3102C6CCC204DAAA6570FD25D8100@TYAPR01MB3102.jpnprd01.prod.outlook.com>
On Fri, Jun 07, 2019 at 08:19:08AM +0000, Yoshihiro Shimoda wrote:
> Hi Christoph,
>
> > From: Christoph Hellwig, Sent: Friday, June 7, 2019 5:08 PM
> >
> > Looks good. And it seems like you've also found the solution to
> > your usb storage problem, but I'm going to post the variant I just
> > hacked up nevertheless.
>
> Thank you for your reply! I think this API is related to my problem,
> but I don't have any actual solution (a patch) for now. So, I'll wait
> for your patch!
Turns out it isn't as simple as I thought, as there doesn't seem to
be an easy way to get to the struct device used for DMA mapping
from USB drivers. I'll need to think a bit more how to handle that
best.
next prev parent reply other threads:[~2019-06-07 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 7:47 [PATCH] Documentation: DMA-API: fix a function name of max_mapping_size Yoshihiro Shimoda
2019-06-07 8:08 ` Christoph Hellwig
2019-06-07 8:19 ` Yoshihiro Shimoda
2019-06-07 8:34 ` Christoph Hellwig [this message]
2019-06-07 12:04 ` Yoshihiro Shimoda
2019-06-07 17:10 ` Jonathan Corbet
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=20190607083447.GA10860@lst.de \
--to=hch@lst.de \
--cc=corbet@lwn.net \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-doc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=yoshihiro.shimoda.uh@renesas.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).