From: Johannes Berg <johannes@sipsolutions.net>
To: Jeff Chen <jeff.chen_1@nxp.com>,
Francesco Dolcini <francesco@dolcini.it>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure in the final build
Date: Mon, 06 Jul 2026 16:52:53 +0200 [thread overview]
Message-ID: <6f2b3e5d82d50d056ddc7dab9355999541b5d1a7.camel@sipsolutions.net> (raw)
In-Reply-To: <akvAuzqXtDrttQk7@sirena.org.uk>
On Mon, 2026-07-06 at 15:50 +0100, Mark Brown wrote:
> Hi all,
>
> In the final build, today's linux-next build (arm64 allyesconfig) failed
> like this:
>
> ld: drivers/net/wireless/nxp/nxpwifi/main.o: in function `is_command_pending':
> main.c:(.text+0xa348): multiple definition of `is_command_pending'; drivers/net/wireless/marvell/mwifiex/main.o:main.c:(.text+0xc188): first defined here
> ld: drivers/net/wireless/nxp/nxpwifi/main.o:(.data+0xa80): multiple definition of `driver_version'; drivers/net/wireless/marvell/mwifiex/main.o:(.rodata+0x2c00): first defined here
> ld: drivers/net/wireless/nxp/nxpwifi/cfp.o:(.data+0x740): multiple definition of `region_code_index'; drivers/net/wireless/marvell/mwifiex/cfp.o:(.data+0x840): first defined here
> ld: drivers/net/wireless/nxp/nxpwifi/wmm.o:(.rodata+0xda0): multiple definition of `tos_to_tid_inv'; drivers/net/wireless/marvell/mwifiex/wmm.o:(.rodata+0xe60): first defined here
>
> due to
>
> 4c477f8bfc1a8 (wifi: nxp: add nxpwifi driver for IW61x)
>
Well. I've dropped the merge then. Jeff, please resend with things fixed
up.
johannes
next prev parent reply other threads:[~2026-07-06 14:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:50 Mark Brown
2026-07-06 14:52 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-30 13:26 Mark Brown
2026-09-30 13:39 ` Thomas Weißschuh
2026-09-25 16:09 Mark Brown
2026-09-28 14:13 ` Mark Brown
2026-09-29 16:07 ` Bjorn Helgaas
2026-09-29 21:18 ` Mark Brown
2026-08-18 20:54 Mark Brown
2026-08-18 23:49 ` Josh Poimboeuf
2026-08-19 8:09 ` Ard Biesheuvel
2026-07-13 17:48 Mark Brown
2026-07-15 15:37 ` Mark Brown
2026-07-17 13:47 ` Manuel Ebner
2026-07-17 14:35 ` Greg Kroah-Hartman
2026-07-17 14:40 ` Johan Hovold
2026-07-17 14:54 ` Mark Brown
2026-07-17 15:06 ` Johan Hovold
2026-07-07 12:11 linux-next: build warnings after merge of the kvm-arm-fixes tree Mark Brown
2026-07-07 12:58 ` linux-next: Build failure in the final build Mark Brown
2026-06-10 15:51 linux-next: build " Mark Brown
2026-01-21 17:14 Mark Brown
2026-01-21 17:18 ` Miguel Ojeda
2026-01-21 17:24 ` Mark Brown
2026-01-21 18:14 ` Miguel Ojeda
2026-01-21 19:14 ` Alice Ryhl
2026-01-21 19:24 ` Miguel Ojeda
2026-01-22 11:20 ` Mark Brown
2026-01-22 0:42 ` Deborah Brouwer
2026-01-22 11:17 ` Mark Brown
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=6f2b3e5d82d50d056ddc7dab9355999541b5d1a7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=francesco@dolcini.it \
--cc=jeff.chen_1@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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
all inboxes | Powered by JetHome®