From: Larry Finger <Larry.Finger@lwfinger.net>
To: nick <xerofoify@gmail.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Non Explained TODOs in halbtcoutsrc.c
Date: Sun, 30 Nov 2014 13:52:31 -0600 [thread overview]
Message-ID: <547B757F.2040900@lwfinger.net> (raw)
In-Reply-To: <547A9F9D.8050103@gmail.com>
On 11/29/2014 10:39 PM, nick wrote:
> Larry,
> Do you known who wrote that code as this I can email them for the explanations for them.
> If not I assume we can remove them as the code makes logical sense unless there are
> hardware or other quirks that need to be handled. :)
> Cheers and Thanks for Your Time,
> Nick
>
> On 2014-11-29 11:31 PM, Larry Finger wrote:
>> On 11/29/2014 05:34 PM, nick wrote:
>>> Greetings Larry,
>>> After reading the code around the TODOS, I can't understand you reasoning for them in this file as they seem to
>>> unneeded as the logic for the switch statement with them seems to be fine. If there are reasons for them in this
>>> file, it would be nice to hear from you on why they are needed as TODO as a comment is rather unclear for anybody
>>> reading this file.
>>> Nick
>>
>> I did not write that code. I merely make it available through the git repo, and modify it so that it will build on all kernel versions. I do not understand the TODOs any more than you do.
>>
>> Larry
Sorry, I do not have permission to reveal the E-mail addresses of any Realtek
software developers. I have added the appropriate developer as a Bcc to this
E-mail. That will leave it up to that individual to respond to you.
Larry
prev parent reply other threads:[~2014-11-30 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <547A581A.7040609@gmail.com>
2014-11-30 4:31 ` Non Explained TODOs in halbtcoutsrc.c Larry Finger
[not found] ` <547A9F9D.8050103@gmail.com>
2014-11-30 19:52 ` 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=547B757F.2040900@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox