From: Kalle Valo <kvalo@codeaurora•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Wireless <linux-wireless@vger•kernel.org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Stanislaw Gruszka <sgruszka@redhat•com>
Subject: Re: linux-next: build failure after merge of the wireless-drivers-next tree
Date: Fri, 03 Aug 2018 12:09:59 +0300 [thread overview]
Message-ID: <874lgb7r4o.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180803182942.4de98df2@canb.auug.org.au> (Stephen Rothwell's message of "Fri, 3 Aug 2018 18:29:42 +1000")
Stephen Rothwell <sfr@canb•auug.org.au> writes:
> After merging the wireless-drivers-next tree, today's linux-next build
> (powerpc allyesconfig) failed like this:
>
> ld: drivers/net/wireless/mediatek/mt76/mt76x0/trace.o:(__tracepoints+0x0): multiple definition of `__tracepoint_set_shared_key'; drivers/net/wireless/mediatek/mt7601u/trace.o:(__tracepoints+0x0): first defined here
[...]
> Caused by commit
>
> 7b4859026ccd ("mt76x0: core files")
>
> and following ones.
>
> I have just marked that driver broken for now:
Thanks Stephen for the report. Odd that kbuild bot didn't catch this, I
did have these patches in my pending branch for several days.
Stanislaw, could you please send a fix for this ASAP? I can't submit a
pull request to Dave until this is fixed.
--
Kalle Valo
next prev parent reply other threads:[~2018-08-03 9:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 8:29 linux-next: build failure after merge of the wireless-drivers-next tree Stephen Rothwell
2018-08-03 9:09 ` Kalle Valo [this message]
2018-08-03 9:11 ` Stanislaw Gruszka
2018-08-03 9:21 ` Stanislaw Gruszka
-- strict thread matches above, loose matches on Subject: below --
2020-12-08 8:49 Stephen Rothwell
2020-12-08 8:54 ` Kalle Valo
2017-06-08 2:27 Stephen Rothwell
2017-06-08 2:43 ` Igor Mitsyanko
2017-06-08 2:57 ` Stephen Rothwell
2017-06-08 12:07 ` Kalle Valo
2017-06-08 12:47 ` Stephen Rothwell
2017-06-13 2:00 ` Stephen Rothwell
2017-06-15 16:08 ` David Miller
2017-06-15 18:25 ` Stephen Rothwell
2016-07-19 6:08 Stephen Rothwell
2016-07-19 6:30 ` Kalle Valo
2016-07-19 6:51 ` Rafał Miłecki
2016-07-19 7:09 ` Kalle Valo
[not found] ` <871t2qw1cz.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2016-07-19 7:11 ` Rafał Miłecki
2016-07-19 14:08 ` Kalle Valo
2016-07-19 18:39 ` Brian Norris
2016-07-19 23:36 ` Stephen Rothwell
2016-07-20 18:31 ` Kalle Valo
2016-02-18 23:10 Stephen Rothwell
2016-02-19 8:08 ` Kalle Valo
2015-08-07 3:16 Stephen Rothwell
2015-08-09 8:41 ` Kalle Valo
2015-07-22 0:32 Stephen Rothwell
2015-07-22 6:07 ` Kalle Valo
2015-07-27 5:41 ` Kalle Valo
2015-07-27 6:04 ` Stephen Rothwell
2015-05-27 2:03 Stephen Rothwell
2015-05-27 9:08 ` Arend van Spriel
2015-05-28 1:38 ` Stephen Rothwell
2015-01-27 8:03 Stephen Rothwell
2015-01-27 8:13 ` Kalle Valo
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=874lgb7r4o.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sgruszka@redhat$(echo .)com \
/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