linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Hans de Goede <hdegoede@redhat.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Jes Sorensen <jes.sorensen@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] staging: Add rtl8723bs sdio wifi driver
Date: Thu, 06 Apr 2017 11:04:52 +0200	[thread overview]
Message-ID: <1491469492.10783.7.camel@hadess.net> (raw)
In-Reply-To: <5d15c6e8-7c15-4226-c4be-d8db6ded29ef@redhat.com>

On Thu, 2017-04-06 at 08:55 +0200, Hans de Goede wrote:
> 
<snip>
> Good thank you. So what is the plan with the github version ?
> 
> Note that my submission contains a few small fixes on top of
> the github version, for which I intended to submit a pull-req
> but I've not gotten around to that yet, I've done so now:
> 
> https://github.com/hadess/rtl8723bs/pull/125
> 
> But do we want to keep maintaining the github version (for a while
> at least) I wonder, as that does mean double work?

My plan is to remove everything and point to the upstream tree as soon
as the support has landed in Linus' tree.

While there is some use in keeping it around for older kernels, we keep
getting asked to support even older kernels than reasonable, or have
users complaining about non-working machines once they use the driver,
which simply uncovers kernel bugs that were fixed upstream.

I don't think it's a good use of our time to carry on supporting this
out-of-tree. I'll however make sure to try and document the migration
in a way that's helpful to users.

Cheers

  reply	other threads:[~2017-04-06  9:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170329174751.13184-1-hdegoede@redhat.com>
2017-03-29 17:54 ` [PATCH] staging: Add rtl8723bs sdio wifi driver Hans de Goede
2017-03-30  1:20 ` Larry Finger
2017-03-30  7:15   ` Greg Kroah-Hartman
2017-03-30 14:06     ` Jes Sorensen
2017-03-30 15:22       ` poma
2017-04-04 18:31 ` Larry Finger
2017-04-04 18:53   ` Hans de Goede
2017-04-04 19:47     ` Larry Finger
2017-04-04 21:38     ` Arend Van Spriel
2017-04-04 21:53       ` Hans de Goede
2017-04-04 23:41         ` Larry Finger
2017-04-05  9:36           ` Hans de Goede
2017-04-05 16:32             ` Larry Finger
2017-04-06  6:55               ` Hans de Goede
2017-04-06  9:04                 ` Bastien Nocera [this message]
2017-04-06  9:49                   ` Hans de Goede
2017-04-06 18:32                     ` Larry Finger
2017-04-06 18:36                       ` 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=1491469492.10783.7.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=arend.vanspriel@broadcom.com \
    --cc=hdegoede@redhat.com \
    --cc=jes.sorensen@gmail.com \
    --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).