From: Joe Perches <joe@perches.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>,
Matthias Beyer <mail@beyermatthias.de>
Cc: gregkh@linuxfoundation.org,
Larry Finger <Larry.Finger@lwfinger.net>,
Manuel Messner <manuel.johannes.messner@hs-furtwangen.de>,
Geliang Tang <geliangtang@163.com>,
Cihangir Akturk <cakturk@gmail.com>,
linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Some cleanup patches for drivers/staging/rtl8723au/core/rtw_mlme.c
Date: Tue, 06 Sep 2016 09:08:48 -0700 [thread overview]
Message-ID: <1473178128.8300.8.camel@perches.com> (raw)
In-Reply-To: <wrfjshtdyq56.fsf@redhat.com>
On Tue, 2016-09-06 at 12:00 -0400, Jes Sorensen wrote:
> Nothing wrong with these patches, however I intend to post a patch to
> remove this driver soon, so it's kind of a waste of your time to spend
> too many cycles on it.
It might be useful to mark any drivers you're
planning on removing as "Obsolete" in MAINTAINERS.
checkpatch will then emit a "don't waste your time"
message if anyone scans an obsolete driver/file.
next prev parent reply other threads:[~2016-09-06 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 19:26 [PATCH 0/5] Some cleanup patches for drivers/staging/rtl8723au/core/rtw_mlme.c Matthias Beyer
2016-09-04 19:26 ` [PATCH 1/5] drivers: staging: rtl8723au: core: Fix checkpatch.pl errors Matthias Beyer
2016-09-04 19:26 ` [PATCH 2/5] drivers: staging: rtl8723au: core: simplify if-break-else Matthias Beyer
2016-09-04 19:26 ` [PATCH 3/5] drivers: staging: rtl8723au: core: Refactor pointless branching Matthias Beyer
2016-09-04 19:26 ` [PATCH 4/5] drivers: staging: rtl8723au: core: Fix "space prohibited" warning Matthias Beyer
2016-09-04 19:26 ` [PATCH 5/5] drivers: staging: rtl8723au: core: Fix indentation Matthias Beyer
2016-09-06 16:00 ` [PATCH 0/5] Some cleanup patches for drivers/staging/rtl8723au/core/rtw_mlme.c Jes Sorensen
2016-09-06 16:08 ` Joe Perches [this message]
2016-09-06 16:11 ` Jes Sorensen
2016-09-07 7:43 ` Matthias Beyer
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=1473178128.8300.8.camel@perches.com \
--to=joe@perches.com \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=cakturk@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=geliangtang@163.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mail@beyermatthias.de \
--cc=manuel.johannes.messner@hs-furtwangen.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.