From: Joe Perches <joe@perches.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Kalle Valo <kvalo@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Driver Project Developer List
<driverdev-devel@linuxdriverproject.org>,
Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] staging: refresh TODO for rtl8723au
Date: Fri, 18 Mar 2016 21:09:58 -0700 [thread overview]
Message-ID: <1458360598.26915.41.camel@perches.com> (raw)
In-Reply-To: <wrfjbn6bi0f9.fsf@redhat.com>
On Fri, 2016-03-18 at 23:58 -0400, Jes Sorensen wrote:
> Joe Perches <joe@perches.com> writes:
> > On Fri, 2016-03-18 at 13:42 -0400, Jes Sorensen wrote:
> > > Xose Vazquez Perez <xose.vazquez@gmail.com> writes:
> > > >
> > > > People should not waste time and energy working on this staging driver.
> > > > A replacement(rtl8xxxu) using the kernel wireless stack already was merged
> > > > in the 4.3 kernel.
> > []
> > >
> > > >
> > > > drivers/staging/rtl8723au/TODO | 3 +++
> > > Acked-by: Jes Sorensen <Jes.Sorensen@redhat.com>
> > why not git rm drivers/staging/rtl8723au/ ?
> Because you don't just pull the rug out under people. I plan to mark it
> obsolete and then remove it in a follow-on release.
Duh.
I note you removed the obsolete suggestion which
is probably more valuable then updating the TODO.
Updating the TODO to something like:
Actual bug fixes only, no other changes accepted.
This driver is going to be removed by 4.8 or so
is also probably more valuable than keeping all the
current items and just adding a note that another
driver exists.
prev parent reply other threads:[~2016-03-19 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 17:15 [PATCH] staging: refresh TODO for rtl8723au Xose Vazquez Perez
2016-03-18 17:42 ` Jes Sorensen
2016-03-18 18:28 ` Joe Perches
2016-03-19 3:58 ` Jes Sorensen
2016-03-19 4:09 ` Joe Perches [this message]
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=1458360598.26915.41.camel@perches.com \
--to=joe@perches.com \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=xose.vazquez@gmail.com \
/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).