From: Christoph Hellwig <hch@lst.de>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, sumit.semwal@linaro.org,
iommu@lists.linux-foundation.org, robin.murphy@arm.com,
hch@lst.de, dan.carpenter@oracle.com
Subject: Re: Passing NULL dev to dma_alloc_coherent() allowed or not?
Date: Sun, 28 Jun 2020 09:10:14 +0200 [thread overview]
Message-ID: <20200628071014.GA16213@lst.de> (raw)
In-Reply-To: <1669515915.65540.1593258316061.JavaMail.zimbra@nod.at>
You can't pass NULL. The synclink case is dead code as we stopped
supporting non-PCI adapters a while ago. I had a patch to remove
the !PCI code a while ago, but it seems like it never made it upstream.
The staging code is, well .. staging code.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Richard Weinberger <richard@nod.at>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
sumit.semwal@linaro.org, robin.murphy@arm.com,
m.szyprowski@samsung.com, hch@lst.de, dan.carpenter@oracle.com
Subject: Re: Passing NULL dev to dma_alloc_coherent() allowed or not?
Date: Sun, 28 Jun 2020 09:10:14 +0200 [thread overview]
Message-ID: <20200628071014.GA16213@lst.de> (raw)
In-Reply-To: <1669515915.65540.1593258316061.JavaMail.zimbra@nod.at>
You can't pass NULL. The synclink case is dead code as we stopped
supporting non-PCI adapters a while ago. I had a patch to remove
the !PCI code a while ago, but it seems like it never made it upstream.
The staging code is, well .. staging code.
next prev parent reply other threads:[~2020-06-28 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 11:45 Passing NULL dev to dma_alloc_coherent() allowed or not? Richard Weinberger
2020-06-27 11:45 ` Richard Weinberger
2020-06-27 13:09 ` Dan Carpenter
2020-06-27 13:09 ` Dan Carpenter
2020-06-28 7:10 ` Christoph Hellwig [this message]
2020-06-28 7:10 ` Christoph Hellwig
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=20200628071014.GA16213@lst.de \
--to=hch@lst.de \
--cc=dan.carpenter@oracle.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=robin.murphy@arm.com \
--cc=sumit.semwal@linaro.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.