All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Greg KH <gregkh@suse.de>,
	devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: remove rtl8187se driver because of lack of development activities
Date: Mon, 09 Nov 2009 11:31:12 -0600	[thread overview]
Message-ID: <4AF851E0.1020803@lwfinger.net> (raw)
In-Reply-To: <20091109145629.3587c9f6@pedra.chehab.org>

On 11/09/2009 10:56 AM, Mauro Carvalho Chehab wrote:
> Hi Bartolomiej,
> 
> Em Mon, 9 Nov 2009 17:31:36 +0100
> Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> escreveu:
> 
>> 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>
> 
> This driver has several points in common with rtl8192* drivers. As I'm
> currently working on cleaning up rtl8192u and see what can be done to merge the
> common code used by all those realtek drivers, I prefer to keep this driver for
> more time at the tree.
> 
> The issue I'm currently facing is that we should rearrange the drivers/staging/rtl* 
> into a common rtl component tree, moving the common components to there. This will
> avoid duplicated efforts to cleanup the same code several times, on different
> places.
> 
> I started working on it this weekend, but I haven't finish it yet.

As I just told Bart (off-list), I started my work on a mainline rtl8187se driver
with the rtl8180 code. There should be plenty of opportunity to set up common
code for the rtl* drivers. I will keep a close eye on your developments.

Larry

      reply	other threads:[~2009-11-09 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 16:31 [PATCH] Staging: remove rtl8187se driver because of lack of development activities Bartlomiej Zolnierkiewicz
2009-11-09 16:49 ` Larry Finger
2009-11-09 16:56 ` Mauro Carvalho Chehab
2009-11-09 17:31   ` Larry Finger [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=4AF851E0.1020803@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --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 \
    --cc=mchehab@infradead.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 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.