public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: 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 13:57:05 -0700	[thread overview]
Message-ID: <47e365e7-60a3-62ea-65e2-e046cbdcc999@infradead.org> (raw)
In-Reply-To: <20220519194922.5d1bac4a@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]



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.


-- 
~Randy

[-- Attachment #2: config-r2921.gz --]
[-- Type: application/gzip, Size: 36438 bytes --]

  reply	other threads:[~2022-05-19 20:57 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 ` Randy Dunlap [this message]
2022-05-19 23:17   ` linux-next: Tree for May 19 (net/ethernet/mellanox/mlx5/core/) Jakub Kicinski

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=47e365e7-60a3-62ea-65e2-e046cbdcc999@infradead.org \
    --to=rdunlap@infradead$(echo .)org \
    --cc=leonro@nvidia$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=saeedm@nvidia$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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