From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: jgg@nvidia.com, Ehab Ababneh <ehab.ababneh@cornelisnetworks.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next] RDMA/hfi1: Depend on !UML
Date: Tue, 12 Jul 2022 12:54:57 +0300 [thread overview]
Message-ID: <Ys1E8fxDpXwl1bMk@unreal> (raw)
In-Reply-To: <165755127879.2996325.5668395672492732376.stgit@awfm-02.cornelisnetworks.com>
On Mon, Jul 11, 2022 at 10:54:38AM -0400, Dennis Dalessandro wrote:
> From: Ehab Ababneh <ehab.ababneh@cornelisnetworks.com>
>
> Both hfi1 and UML depend on x86_64, this can trigger build errors.
> This driver must depends on !UML because it accesses x86_64
> features that are not supported by UML.
>
> Signed-off-by: Ehab Ababneh <ehab.ababneh@cornelisnetworks.com>
> Signed-off-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
> ---
> drivers/infiniband/hw/hfi1/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)a
But why is this hfi1 specific change?
Shouldn't CONFIG_UML be disabled if someone choses !x86_64?
Thanks
>
> diff --git a/drivers/infiniband/hw/hfi1/Kconfig b/drivers/infiniband/hw/hfi1/Kconfig
> index 6eb739052121..14b92e12bf29 100644
> --- a/drivers/infiniband/hw/hfi1/Kconfig
> +++ b/drivers/infiniband/hw/hfi1/Kconfig
> @@ -1,7 +1,7 @@
> # SPDX-License-Identifier: GPL-2.0-only
> config INFINIBAND_HFI1
> tristate "Cornelis OPX Gen1 support"
> - depends on X86_64 && INFINIBAND_RDMAVT && I2C
> + depends on X86_64 && INFINIBAND_RDMAVT && I2C && !UML
> select MMU_NOTIFIER
> select CRC32
> select I2C_ALGOBIT
>
>
next prev parent reply other threads:[~2022-07-12 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 14:54 [PATCH for-next] RDMA/hfi1: Depend on !UML Dennis Dalessandro
2022-07-12 9:54 ` Leon Romanovsky [this message]
2022-07-12 12:33 ` Dennis Dalessandro
2022-07-13 6:57 ` Leon Romanovsky
2022-07-18 10:41 ` Leon Romanovsky
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=Ys1E8fxDpXwl1bMk@unreal \
--to=leon@kernel.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=ehab.ababneh@cornelisnetworks.com \
--cc=jgg@nvidia.com \
--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