From: patchwork-bot+netdevbpf@kernel.org
To: Robin Murphy <robin.murphy@arm.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ecree.xilinx@gmail.com, iommu@lists.linux-foundation.org,
habetsm.xilinx@gmail.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [PATCH net-next] sfc: Stop using iommu_present()
Date: Fri, 08 Apr 2022 04:10:12 +0000 [thread overview]
Message-ID: <164939101209.29309.3949750124677153031.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <7350f957944ecfce6cce90f422e3992a1f428775.1649166055.git.robin.murphy@arm.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 5 Apr 2022 14:40:55 +0100 you wrote:
> Even if an IOMMU might be present for some PCI segment in the system,
> that doesn't necessarily mean it provides translation for the device
> we care about. It appears that what we care about here is specifically
> whether DMA mapping ops involve any IOMMU overhead or not, so check for
> translation actually being active for our device.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>
> [...]
Here is the summary with links:
- [net-next] sfc: Stop using iommu_present()
https://git.kernel.org/netdev/net-next/c/6a62924c0a81
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2022-04-08 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 13:40 [PATCH net-next] sfc: Stop using iommu_present() Robin Murphy
2022-04-07 16:05 ` Edward Cree
2022-04-08 4:10 ` patchwork-bot+netdevbpf [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=164939101209.29309.3949750124677153031.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=habetsm.xilinx@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robin.murphy@arm.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