[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f01f0019-2e52-bad5-2774-76863960de72@infradead.org>
Date: Tue, 31 Mar 2020 09:39:01 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Saeed Mahameed <saeedm@...lanox.com>,
Leon Romanovsky <leonro@...lanox.com>
Subject: Re: linux-next: Tree for Mar 31 (mlx5)
On 3/31/20 2:10 AM, Stephen Rothwell wrote:
> Hi all,
>
> The merge window has opened, so please do not add any material for the
> next release into your linux-next included trees/branches until after
> the merge window closes.
>
> Changes since 20200330:
>
on x86_64:
ld: drivers/net/ethernet/mellanox/mlx5/core/main.o: in function `mlx5_cleanup_once':
main.c:(.text+0x1ca): undefined reference to `mlx5_vxlan_destroy'
ld: main.c:(.text+0x1d2): undefined reference to `mlx5_cleanup_clock'
ld: drivers/net/ethernet/mellanox/mlx5/core/main.o: in function `mlx5_load_one':
main.c:(.text+0xf44): undefined reference to `mlx5_init_clock'
ld: main.c:(.text+0xf4c): undefined reference to `mlx5_vxlan_create'
ld: main.c:(.text+0xfe5): undefined reference to `mlx5_vxlan_destroy'
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@...radead.org>
View attachment "config-next-mlx5" of type "text/plain" (165062 bytes)
Powered by blists - more mailing lists