From: Greg Kroah-Hartman <greg@kroah.com>
To: Maxim Mikityanskiy <maxtram95@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Need help with RTL8187SE staging driver
Date: Sun, 11 Nov 2012 16:10:34 -0800 [thread overview]
Message-ID: <20121112001034.GA1150@kroah.com> (raw)
In-Reply-To: <CAKErNvq9O5d_vEQnBhD6PSy-gc37UfvhRA4nRh1r=xFSdC98Yw@mail.gmail.com>
On Sun, Nov 11, 2012 at 11:48:46PM +0200, Maxim Mikityanskiy wrote:
> (I'm sorry, mailing list rejected my previous letter, I'm resending)
>
> Hello,
>
> I've decided to refactor and improve rtl8187se kernel driver from
> staging directory, because it is buggy and lacks some features. It
> causes full system freeze after resume from suspend, there are some
> typos in interrupt handler that affect logic, it causes OOPS when
> rmmoding, it has not rfkill support, it uses private ieee80211 stack
> etc.
>
> I'm writing to you, because your address is mentioned in
> drivers/staging/rtl8187se/TODO file. Also I'm CCing to linux-wireless
> mailing list in hope that there are people that could also help me.
>
> You can clone git repository with modified driver source code here:
> git@bitbucket.org:gentoo_root/
> rtl8187se-staging.git. At first, I've removed some non-vital features
> and dead code from original driver in order to simplify code. Then
> I've fixed some bugs and created more clear structure of code. For
> now, I did not fully follow Linux kernel coding style, there are lots
> of long lines, and I hope to fix that later.
Why not send patches for this so we can get your cleanups and other dead
code removal changes into the tree to make your further changes easier?
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-12 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKErNvpyUxNxEMEt6gcVCr_3MTNpHaSU=5yZy2YsYmYOSCJLsw@mail.gmail.com>
2012-11-11 21:48 ` Need help with RTL8187SE staging driver Maxim Mikityanskiy
2012-11-12 0:10 ` Greg Kroah-Hartman [this message]
2012-11-12 17:55 ` Maxim Mikityanskiy
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=20121112001034.GA1150@kroah.com \
--to=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maxtram95@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 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.