[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c92d20e27268f515e0d4c8a28f92c0da041c2acc.camel@mellanox.com>
Date: Thu, 29 Aug 2019 21:31:49 +0000
From: Saeed Mahameed <saeedm@...lanox.com>
To: "sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
Eran Ben Elisha <eranbe@...lanox.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
haiyangz <haiyangz@...rosoft.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Leon Romanovsky <leonro@...lanox.com>
Subject: Re: linux-next: Tree for Aug 29 (mlx5)
On Thu, 2019-08-29 at 12:55 -0700, Randy Dunlap wrote:
> On 8/29/19 12:54 PM, Randy Dunlap wrote:
> > On 8/29/19 4:08 AM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20190828:
> > >
> >
> > on x86_64:
> > when CONFIG_PCI_HYPERV=m
>
> and CONFIG_PCI_HYPERV_INTERFACE=m
>
Haiyang and Eran, I think CONFIG_PCI_HYPERV_INTERFACE was never
supposed to be a module ? it supposed to provide an always available
interface to drivers ..
Anyway, maybe we need to imply CONFIG_PCI_HYPERV_INTERFACE in mlx5.
Thanks,
Saeed.
> > and mxlx5 is builtin (=y).
> >
> > ld: drivers/net/ethernet/mellanox/mlx5/core/main.o: in function
> > `mlx5_unload':
> > main.c:(.text+0x5d): undefined reference to `mlx5_hv_vhca_cleanup'
> > ld: drivers/net/ethernet/mellanox/mlx5/core/main.o: in function
> > `mlx5_cleanup_once':
> > main.c:(.text+0x158): undefined reference to `mlx5_hv_vhca_destroy'
> > ld: drivers/net/ethernet/mellanox/mlx5/core/main.o: in function
> > `mlx5_load_one':
> > main.c:(.text+0x4191): undefined reference to `mlx5_hv_vhca_create'
> > ld: main.c:(.text+0x4772): undefined reference to
> > `mlx5_hv_vhca_init'
> > ld: main.c:(.text+0x4b07): undefined reference to
> > `mlx5_hv_vhca_cleanup'
> >
> >
>
>
Powered by blists - more mailing lists