From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, larry.finger@lwfinger.net
Subject: Re: pull request: wireless-next 2014-10-03
Date: Tue, 7 Oct 2014 10:18:44 -0400 [thread overview]
Message-ID: <20141007141844.GH25590@tuxdriver.com> (raw)
In-Reply-To: <20141007.004724.187788111776188480.davem@davemloft.net>
On Tue, Oct 07, 2014 at 12:47:24AM -0400, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Sun, 05 Oct 2014 21:38:53 -0400 (EDT)
>
> > From: David Miller <davem@davemloft.net>
> > Date: Sun, 05 Oct 2014 21:35:11 -0400 (EDT)
> >
> >> From: "John W. Linville" <linville@tuxdriver.com>
> >> Date: Fri, 3 Oct 2014 14:01:52 -0400
> >>
> >>> Please pull tihs batch of updates intended for the 3.18 stream!
> >>
> >> Pulled, thanks for the stellar pull request text, as always.
> >
> > John, what's the deal with the following? Will it be resolved by the
> > driver being removed from the staging tree?
> >
> > WARNING: drivers/staging/rtl8192ee/r8192ee: 'rtl_evm_dbm_jaguar' exported twice. Previous export was in drivers/net/wireless/rtlwifi/rtlwifi.ko
>
> John, ping?
Sorry, Dave -- sendmail died on my local machine and I didn't notice
until now... :-(
Anyway...yes, the staging driver should be removed by a patch in
Greg's queue.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-10-07 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 18:01 pull request: wireless-next 2014-10-03 John W. Linville
2014-10-06 1:35 ` David Miller
2014-10-06 1:38 ` David Miller
2014-10-06 15:00 ` John W. Linville
2014-10-07 4:47 ` David Miller
2014-10-07 14:18 ` John W. Linville [this message]
2014-10-07 14:45 ` Larry Finger
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=20141007141844.GH25590@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).