From: Larry Finger <Larry.Finger@lwfinger.net>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Greg KH <gregkh@suse.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org,
Bernhard Schiffner <bernhard@schiffner-limbach.de>
Subject: Re: [PATCH] Staging: remove rtl8187se driver because of lack of development activities
Date: Mon, 09 Nov 2009 10:49:44 -0600 [thread overview]
Message-ID: <4AF84828.7070807@lwfinger.net> (raw)
In-Reply-To: <200911091731.36861.bzolnier@gmail.com>
On 11/09/2009 10:31 AM, Bartlomiej Zolnierkiewicz wrote:
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Subject: [PATCH] Staging: remove rtl8187se driver because of lack of development activities
>
> This driver hasn't seen any real development activities since early July:
>
> 257bc86 Staging: rtl8187se: remove unused #include <linu
> 2035beb param:remove-useless-writable-charp
> 305409a tree-wide: fix some typos and punctuation in com
> b881c6c Staging: fix wireless drivers depends
> a010a33 Staging: rtl8187se/rtl8192e/rtl8192su: allow mod
> 125b181 staging: Add proper selection of WIRELESS_EXT an
> b3184e1 Staging: rtl8187se: Fix comment-out-typo
> b6ac161 Staging: ARRAY_SIZE changes
>
> so remove it for now.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
NACK. I am currently using this driver as a template for the development of a
mainline rtl8187se driver. Removing the staging version would not matter to me,
but it would complicate matters for my tester (Bernhard Schiffner
<bernhard@schiffner-limbach.de>). I do not have the hardware, thus I rely on his
help.
Larry
next prev parent reply other threads:[~2009-11-09 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 16:31 Bartlomiej Zolnierkiewicz
2009-11-09 16:49 ` Larry Finger [this message]
2009-11-09 16:56 ` Mauro Carvalho Chehab
2009-11-09 17:31 ` 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=4AF84828.7070807@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bernhard@schiffner-limbach.de \
--cc=bzolnier@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®