From: John Daiker <daikerjohn@gmail.com>
To: Markus Becker <mab@comnets.uni-bremen.de>
Cc: Pavel Roskin <proski@gnu.org>, linux-wireless@vger.kernel.org
Subject: Re: First patch to mrv8k driver?
Date: Wed, 14 May 2008 10:56:30 -0700 [thread overview]
Message-ID: <482B27CE.2070700@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805141506000.24384@bugs.comnets.uni-bremen.de>
Markus Becker wrote:
>
> On Wed, 14 May 2008, Pavel Roskin wrote:
>
>> On Tue, 2008-05-13 at 17:59 -0700, John Daiker wrote:
>>> Hey All,
>>>
>>> My first patch for the mrv8k driver. My machine locks up when I try to
>>> load a firmware, so I'm not sure if this patch helps anybody or not.
>>
>> I don't see any changes for mrv_reg_read32() claimed in the description.
>
> He is checking the return value to 0x5 instead of 5.
Right... the aim here is for some sort of code consistency. Makes
things easier to read, IMHO.
>
>> In fact, I don't see any changes to the code except comments and
>> messages. I don't see how it can help against lockups, unless you
>> missed some part of the patch.
>
> It does not. But I pushed the comment and indent fixes to mrv8k
> nevertheless.
Thanks. I guess I mentioned that to solicit input from others on ideas
for debugging.
>
>> You may want to spell check your patch, including the description,
>> especially if the patch is fixing spelling mistakes made by others.
Duly noted. I will keep an keen eye out next time for mistakes. :)
>>
>> --
>> Regards,
>> Pavel Roskin
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
prev parent reply other threads:[~2008-05-14 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 0:59 First patch to mrv8k driver? John Daiker
2008-05-14 4:37 ` Pavel Roskin
2008-05-14 13:08 ` Markus Becker
2008-05-14 13:21 ` Johannes Berg
2008-05-14 17:56 ` John Daiker [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=482B27CE.2070700@gmail.com \
--to=daikerjohn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mab@comnets.uni-bremen.de \
--cc=proski@gnu.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.