From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "John W. Linville" <linville@tuxdriver•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Larry Finger <Larry.Finger@lwfinger•net>,
Greg KH <greg@kroah•com>
Subject: linux-next: build warning after merge of the wireless-next tree
Date: Tue, 30 Sep 2014 18:46:07 +1000 [thread overview]
Message-ID: <20140930184607.081d38de@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
Hi John,
After merging the wireless-next tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
WARNING: drivers/staging/rtl8192ee/r8192ee: 'rtl_evm_dbm_jaguar' exported twice. Previous export was in drivers/net/wireless/rtlwifi/rtlwifi.ko
Introduced by commit f3a97e93814a ("rtlwifi: Finish modifying core
routines for new drivers").
I suspect that there is a staging driver that needs removing/updating?
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-09-30 8:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 8:46 Stephen Rothwell [this message]
2014-09-30 14:41 ` linux-next: build warning after merge of the wireless-next tree Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 3:29 Stephen Rothwell
2024-02-09 7:06 ` Johannes Berg
2023-09-14 2:49 Stephen Rothwell
2023-09-12 5:10 Stephen Rothwell
2023-03-23 3:15 Stephen Rothwell
2023-03-31 11:10 ` Kalle Valo
2023-02-15 4:20 Stephen Rothwell
2023-02-15 4:17 Stephen Rothwell
2023-01-19 5:24 Stephen Rothwell
2022-06-21 10:02 Stephen Rothwell
2022-05-17 10:00 Stephen Rothwell
2022-05-18 4:51 ` Kalle Valo
2013-04-05 5:46 Stephen Rothwell
2013-04-04 1:00 Stephen Rothwell
2013-04-04 1:04 ` Stephen Rothwell
2013-04-04 1:17 ` Larry Finger
2013-04-04 2:36 ` Stephen Rothwell
2013-04-04 2:58 ` Larry Finger
2011-11-22 3:25 Stephen Rothwell
2011-11-22 7:56 ` Stanislaw Gruszka
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=20140930184607.081d38de@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Larry.Finger@lwfinger$(echo .)net \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(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