From: "Bernard Metzler" <BMT@zurich.ibm.com>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Doug Ledford" <dledford@redhat.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Jason Gunthorpe" <jgg@mellanox.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rdma/siw: select CONFIG_DMA_VIRT_OPS
Date: Fri, 12 Jul 2019 11:36:58 +0000 [thread overview]
Message-ID: <OFFAD5C366.21FE2E97-ON00258435.003FCF45-00258435.003FCF4A@notes.na.collabserv.com> (raw)
In-Reply-To: <20190712085253.3965945-1-arnd@arndb.de>
Hi Arnd, this got already fixed.
Many thanks!
Bernard.
-----"Arnd Bergmann" <arnd@arndb.de> wrote: -----
>To: "Bernard Metzler" <bmt@zurich.ibm.com>, "Doug Ledford"
><dledford@redhat.com>, "Jason Gunthorpe" <jgg@ziepe.ca>
>From: "Arnd Bergmann" <arnd@arndb.de>
>Date: 07/12/2019 10:53AM
>Cc: "Arnd Bergmann" <arnd@arndb.de>, "Jason Gunthorpe"
><jgg@mellanox.com>, linux-rdma@vger.kernel.org,
>linux-kernel@vger.kernel.org
>Subject: [EXTERNAL] [PATCH] rdma/siw: select CONFIG_DMA_VIRT_OPS
>
>Without this symbol we get a link failure:
>
>ERROR: "dma_virt_ops" [drivers/infiniband/sw/siw/siw.ko] undefined!
>
>Fixes: bdcf26bf9b3a ("rdma/siw: network and RDMA core interface")
>Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>---
> drivers/infiniband/sw/siw/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/drivers/infiniband/sw/siw/Kconfig
>b/drivers/infiniband/sw/siw/Kconfig
>index 94f684174ce3..ea282789f466 100644
>--- a/drivers/infiniband/sw/siw/Kconfig
>+++ b/drivers/infiniband/sw/siw/Kconfig
>@@ -1,6 +1,7 @@
> config RDMA_SIW
> tristate "Software RDMA over TCP/IP (iWARP) driver"
> depends on INET && INFINIBAND && CRYPTO_CRC32
>+ select DMA_VIRT_OPS
> help
> This driver implements the iWARP RDMA transport over
> the Linux TCP/IP network stack. It enables a system with a
>--
>2.20.0
>
>
prev parent reply other threads:[~2019-07-12 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 8:52 Arnd Bergmann
2019-07-12 11:36 ` Bernard Metzler [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=OFFAD5C366.21FE2E97-ON00258435.003FCF45-00258435.003FCF4A@notes.na.collabserv.com \
--to=bmt@zurich.ibm.com \
--cc=arnd@arndb.de \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®