From: Larry Finger <Larry.Finger@lwfinger.net>
To: Nick Krause <xerofoify@gmail.com>, Joe Perches <joe@perches.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, pebolle@tiscali.nl,
Himangi Saraogi <himangi774@gmail.com>,
Konrad Zapalowicz <bergo.torino@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging:rtl8821ae: rewrite legacy wifi check in halbcoutsrc
Date: Sat, 21 Jun 2014 08:06:23 -0500 [thread overview]
Message-ID: <53A5834F.8050805@lwfinger.net> (raw)
In-Reply-To: <CAPDOMVgyttC0AY8CUbWESSBKpkskJYjC3L1AcPw_s0q=QJjLoQ@mail.gmail.com>
On 06/20/2014 09:52 PM, Nick Krause wrote:
> Is this patch being merged or is this not an issue. I am confused
> did I make a mistake in my patch or is there being a different
> patch being merged.
> Thank Nick
>
> On Fri, Jun 20, 2014 at 10:34 PM, Joe Perches <joe@perches.com> wrote:
>> On Fri, 2014-06-20 at 22:26 -0400, Nick Krause wrote:
>>> Thanks for the feedback I will resend the patch fixed.
>>
>> Please do not.
>>
>>> Otherwise please use Larry's idea.
>>
>> It's not Larry's idea. Larry is the primary
>> contributor for Realtek drivers in staging.
I have just returned from back-to-back trips and a recovery from the failure of
my primary laptop. Once I get a little time, I will research this issue and let
you know. In the meantime, this patch should not be merged as it is not likely
correct.
Larry
next prev parent reply other threads:[~2014-06-21 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 16:56 [PATCH] staging:rtl8821ae: rewrite legacy wifi check in halbcoutsrc Nicholas Krause
2014-06-20 19:59 ` Dan Carpenter
2014-06-20 20:08 ` Joe Perches
2014-06-21 2:26 ` Nick Krause
2014-06-21 2:34 ` Joe Perches
2014-06-21 2:52 ` Nick Krause
2014-06-21 13:06 ` Larry Finger [this message]
[not found] ` <CAPDOMVgvnNkVc9TN4MHm7UaD+nfac8C6A0kMo=q9Q237nTWUKQ@mail.gmail.com>
2014-06-21 20:14 ` Greg KH
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=53A5834F.8050805@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bergo.torino@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=himangi774@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=xerofoify@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.