From: Alexandre Becholey <alexandre@shockfish.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH]rt73usb: fix for master mode.
Date: Mon, 18 May 2009 16:42:25 +0200 [thread overview]
Message-ID: <4A1173D1.5010704@shockfish.com> (raw)
In-Reply-To: <200905181531.37484.IvDoorn@gmail.com>
Ivo van Doorn wrote:
> On Monday 18 May 2009, Alexandre Becholey wrote:
>
>> Report status unknown as if there were successfully transmitted.
>> This will avoid hostapd to disassociate because it doesn't understand what a status unknown is.
>>
>> Signed-off-by: Alexandre Becholey <alexandre.becholey@epfl.ch>
>> ---
>> drivers/net/wireless/rt2x00/rt2x00dev.c | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>
> Please put your patches inline, and CC me for rt2x00 related patches.
>
Yep sorry I forgot to CC you :-/
Oups I forgot an --inline in the git-format-patch
> As for the patch it seems like you indented with spaces rather then tabs?
>
Sorry first time I submitted a patch... I use vim and I use tabs that's
strange.
I'll restart from the original file.
> And please put the comment inside the else statement rather then breaking
> the if-elseif-elseif list.
>
> Also have you considered the following things:
> RTS frames success/failure reporting?
> tx_success/tx_failure statistics counters (used in link_tuner as well)
>
> Thanks,
>
> Ivo
>
Ok I'll do it, but how should I treat the status unknown for the
statistics? as a success?
Alexandre
next prev parent reply other threads:[~2009-05-18 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 12:55 [PATCH]rt73usb: fix for master mode Alexandre Becholey
2009-05-18 13:17 ` John W. Linville
2009-05-18 13:31 ` Ivo van Doorn
2009-05-18 14:42 ` Alexandre Becholey [this message]
2009-05-18 14:45 ` Ivo van Doorn
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=4A1173D1.5010704@shockfish.com \
--to=alexandre@shockfish.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).