From: Jakub Kicinski <kuba@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Leon Romanovsky <leonro@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: linux-next: Tree for May 19 (net/ethernet/mellanox/mlx5/core/)
Date: Thu, 19 May 2022 16:17:26 -0700 [thread overview]
Message-ID: <20220519161726.08cd9301@kernel.org> (raw)
In-Reply-To: <47e365e7-60a3-62ea-65e2-e046cbdcc999@infradead.org>
On Thu, 19 May 2022 13:57:05 -0700 Randy Dunlap wrote:
> On 5/19/22 02:49, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20220518:
>
> on i386 or x86_64:
>
> drivers/net/ethernet/mellanox/mlx5/core/lag/lag.o: in function `mlx5_lag_mpesw_init':
> lag.c:(.text+0x408): multiple definition of `mlx5_lag_mpesw_init'; ld: DWARF error: could not find abbrev number 25
> drivers/net/ethernet/mellanox/mlx5/core/lag/debugfs.o:debugfs.c:(.text+0x41c): first defined here
> ld: drivers/net/ethernet/mellanox/mlx5/core/lag/lag.o: in function `mlx5_lag_mpesw_cleanup':
> lag.c:(.text+0x40e): multiple definition of `mlx5_lag_mpesw_cleanup'; drivers/net/ethernet/mellanox/mlx5/core/lag/debugfs.o:debugfs.c:(.text+0x422): first defined here
>
>
> x86_64 randconfig file is attached.
Thanks, should be fixed by commit d935053a62fa ("net/mlx5: fix multiple
definitions of mlx5_lag_mpesw_init / mlx5_lag_mpesw_cleanup") in net-next.
prev parent reply other threads:[~2022-05-19 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 9:49 linux-next: Tree for May 19 Stephen Rothwell
2022-05-19 20:57 ` linux-next: Tree for May 19 (net/ethernet/mellanox/mlx5/core/) Randy Dunlap
2022-05-19 23:17 ` Jakub Kicinski [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=20220519161726.08cd9301@kernel.org \
--to=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=saeedm@nvidia.com \
--cc=sfr@canb.auug.org.au \
/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.