From: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org,
"Hin-Tak Leung" <htl10@users.sourceforge.net>,
John W Linville <linville@tuxdriver.com>,
Michael Wu <flamingice@sourmilk.net>,
Andrea Merello <andrea.merello@gmail.com>
Subject: Re: [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B
Date: Wed, 5 Nov 2008 13:59:50 -0200 [thread overview]
Message-ID: <200811051359.51665.herton@mandriva.com.br> (raw)
In-Reply-To: <1225899623.3619.119.camel@johannes.berg>
On Wednesday 05 November 2008 13:40:22 Johannes Berg wrote:
> On Wed, 2008-11-05 at 13:38 -0200, Herton Ronaldo Krzesinski wrote:
> > > > WARNING: line over 80 characters
> > > > #138: FILE: drivers/net/wireless/rtl8187_dev.c:475:
> > > > + if ((le16_to_cpu(ieee80211hdr->seq_ctrl) &
> > > > 0xFFF) == seq_no)
> >
> > Ops, I forgot to run checkpatch.pl here, will run and fix it when I
> > submit next patch.
>
> I wouldn't worry about lines > 80 chars too much, breaking this down
> wouldn't make more readable but less so, in my opinion. I tend to ignore
> that rule where it makes the code unreadable :)
>
> > > Besides, that line looks wrong? the lowest 4 bits are teh fragment
> > > number.
> >
> > It's intended, because the hardware instead of reporting just the
> > sequence number in its 12 bits is reporting fragment number + sequence
> > number, this is a workaround.
>
> Ah. A comment might be appropriate that "seq_no" doesn't actually
> contain the sequence number?
Yes, I'll improve comment there, will change by this:
/*
* While testing, it was discovered that the seq_no doesn't
* actually contains the sequence number. Instead
* of returning just the 12 bits of sequence number,
* hardware is returning entire sequence control (fragment
* number plus sequence number) in a 12 bit only field
* overflowing after some time. As a workaround,
* just consider the lower bits, and expect it's unlikely
* we wrongly ack some sent data
*/
>
> johannes
--
[]'s
Herton
next prev parent reply other threads:[~2008-11-05 15:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 13:50 [RFC/RFT PATCH 0/2 v2] rtl8187: implement conf_tx callback/correctly ack tx pkts Herton Ronaldo Krzesinski
2008-11-04 13:50 ` [RFC/RFT PATCH v2 1/2] rtl8187: implement conf_tx callback to configure tx queues Herton Ronaldo Krzesinski
2008-11-04 22:30 ` Larry Finger
2008-11-04 23:11 ` Felix Fietkau
2008-11-05 15:33 ` Herton Ronaldo Krzesinski
2008-11-04 13:50 ` [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B Herton Ronaldo Krzesinski
2008-11-04 20:27 ` Hin-Tak Leung
2008-11-04 21:30 ` Herton Ronaldo Krzesinski
2008-11-04 22:31 ` Larry Finger
2008-11-05 11:29 ` Johannes Berg
2008-11-05 15:38 ` Herton Ronaldo Krzesinski
2008-11-05 15:40 ` Johannes Berg
2008-11-05 15:59 ` Herton Ronaldo Krzesinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-05 2:02 Hin-Tak Leung
2008-11-05 15:42 ` Herton Ronaldo Krzesinski
2008-11-05 17:11 ` Hin-Tak Leung
2008-11-05 21:36 ` Herton Ronaldo Krzesinski
2008-11-05 22:05 ` Hin-Tak Leung
2008-11-05 22:43 ` Luis R. Rodriguez
2008-11-05 23:16 ` Hin-Tak Leung
2008-11-05 23:35 ` Luis R. Rodriguez
2008-11-06 14:14 ` John W. Linville
2008-11-06 18:53 ` Luis R. Rodriguez
2008-11-06 0:00 ` Hin-Tak Leung
2008-11-06 0:18 ` Larry Finger
2008-11-06 1:02 ` Hin-Tak Leung
2008-11-06 1:36 ` Hin-Tak Leung
2008-11-06 1:42 ` Larry Finger
2008-11-06 4:23 ` Hin-Tak Leung
2008-11-06 20:49 ` Hin-Tak Leung
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=200811051359.51665.herton@mandriva.com.br \
--to=herton@mandriva.com.br \
--cc=Larry.Finger@lwfinger.net \
--cc=andrea.merello@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=htl10@users.sourceforge.net \
--cc=johannes@sipsolutions.net \
--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).