linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/1] rtl8xxxu (mac80211) driver for rtl8188[cr]u/rtl8192cu/rtl8723au
Date: Tue, 08 Sep 2015 17:04:04 -0400	[thread overview]
Message-ID: <wrfjr3m8aaij.fsf@redhat.com> (raw)
In-Reply-To: <55EDAEC9.701@lwfinger.net> (Larry Finger's message of "Mon, 7 Sep 2015 10:35:37 -0500")

Larry Finger <Larry.Finger@lwfinger.net> writes:
> On 09/07/2015 04:06 AM, Kalle Valo wrote:
>> Larry Finger <Larry.Finger@lwfinger.net> writes:
>> Ok. Can't we start just rtl8xxxu having just devices NOT supported by
>> rtlwifi drivers? All other devices would be under
>> CONFIG_RTL8XXXU_UNTESTED until we think the support is ready and we can
>> make the switch by moving from untested to tested category. And at the
>> same time disable/remove those devices from rtlwifi.
>
> Yes, that will work as long as we make CONFIG_RTL8XXXU_UNTESTED be
> EXPERIMENTAL to keep the distros from enabling it. In addition, a
> separate GitHub repo for rtl8xxxu should be made available with
> conditional code added to enable builds for kernels 3.10 or
> later. Then users that complain about some problem with rtl8192cu can
> be directed to that driver.

If someone wants to maintain a backported version of the driver for
certain kernels, that is fine with me. It should probably be in the form
of an out-of tree build package, so maybe simply a tarball would
suffice?

Cheers,
Jes

  reply	other threads:[~2015-09-08 21:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30 21:02 [PATCH v2 0/1] rtl8xxxu (mac80211) driver for rtl8188[cr]u/rtl8192cu/rtl8723au Jes.Sorensen
2015-08-30 21:02 ` [PATCH 1/1] New driver: rtl8xxxu (mac80211) Jes.Sorensen
2015-09-06 14:59   ` Kalle Valo
2015-09-06 17:06     ` Larry Finger
2015-09-07  1:41       ` Jes Sorensen
2015-09-07  1:40     ` Jes Sorensen
2015-09-07 13:20       ` Kalle Valo
2015-09-07 21:08         ` Jes Sorensen
2015-09-06 14:43 ` [PATCH v2 0/1] rtl8xxxu (mac80211) driver for rtl8188[cr]u/rtl8192cu/rtl8723au Kalle Valo
2015-09-06 17:03   ` Larry Finger
2015-09-07  9:06     ` Kalle Valo
2015-09-07 15:35       ` Larry Finger
2015-09-08 21:04         ` Jes Sorensen [this message]
2015-09-08 21:13       ` Jes Sorensen
2015-09-08 21:01     ` Jes Sorensen
2015-09-09 10:51       ` Bruno Randolf
2015-09-07  1:45   ` Jes Sorensen
2015-09-07  4:24     ` Jes Sorensen
2015-09-07  8:53       ` Kalle Valo
2015-09-07  9:17     ` Kalle Valo
2015-09-08 21:24       ` Jes Sorensen

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=wrfjr3m8aaij.fsf@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@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).