From: Jason Gunthorpe via iommu <iommu@lists.linux-foundation.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: neescoba@cisco.com, linux-rdma@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
benve@cisco.com
Subject: Re: [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd()
Date: Fri, 8 Apr 2022 14:23:00 -0300 [thread overview]
Message-ID: <20220408172300.GC3637956@nvidia.com> (raw)
In-Reply-To: <ef607cb3f5a09920b86971b8c8e60af8c647457e.1649169359.git.robin.murphy@arm.com>
On Tue, Apr 05, 2022 at 03:35:59PM +0100, Robin Murphy wrote:
> Rather than hard-coding pci_bus_type, pass the PF device through to
> usnic_uiom_alloc_pd() and retrieve its bus there. This prepares for
> iommu_domain_alloc() changing to take a device rather than a bus_type.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> Reported-by: kernel test robot <lkp@intel.com>
> ---
> drivers/infiniband/hw/usnic/usnic_ib_verbs.c | 3 +--
> drivers/infiniband/hw/usnic/usnic_uiom.c | 5 ++---
> drivers/infiniband/hw/usnic/usnic_uiom.h | 2 +-
> 3 files changed, 4 insertions(+), 6 deletions(-)
Applied to for-next, thanks
Jason
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: benve@cisco.com, neescoba@cisco.com, linux-rdma@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd()
Date: Fri, 8 Apr 2022 14:23:00 -0300 [thread overview]
Message-ID: <20220408172300.GC3637956@nvidia.com> (raw)
In-Reply-To: <ef607cb3f5a09920b86971b8c8e60af8c647457e.1649169359.git.robin.murphy@arm.com>
On Tue, Apr 05, 2022 at 03:35:59PM +0100, Robin Murphy wrote:
> Rather than hard-coding pci_bus_type, pass the PF device through to
> usnic_uiom_alloc_pd() and retrieve its bus there. This prepares for
> iommu_domain_alloc() changing to take a device rather than a bus_type.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> Reported-by: kernel test robot <lkp@intel.com>
> ---
> drivers/infiniband/hw/usnic/usnic_ib_verbs.c | 3 +--
> drivers/infiniband/hw/usnic/usnic_uiom.c | 5 ++---
> drivers/infiniband/hw/usnic/usnic_uiom.h | 2 +-
> 3 files changed, 4 insertions(+), 6 deletions(-)
Applied to for-next, thanks
Jason
next prev parent reply other threads:[~2022-04-08 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 14:35 [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd() Robin Murphy
2022-04-05 14:35 ` Robin Murphy
2022-04-06 19:54 ` kernel test robot
2022-04-06 19:54 ` kernel test robot
2022-04-06 21:39 ` Robin Murphy
2022-04-06 21:39 ` Robin Murphy
2022-04-06 21:39 ` Robin Murphy
2022-04-06 21:53 ` Jason Gunthorpe
2022-04-06 21:53 ` Jason Gunthorpe
2022-04-06 21:53 ` Jason Gunthorpe
2022-04-08 17:23 ` Jason Gunthorpe via iommu [this message]
2022-04-08 17:23 ` Jason Gunthorpe
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=20220408172300.GC3637956@nvidia.com \
--to=iommu@lists.linux-foundation.org \
--cc=benve@cisco.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=neescoba@cisco.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 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.