From: Johannes Berg <johannes@sipsolutions.net>
To: Zhu Yi <yi.zhu@intel.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 1/2] wireless: add ieee80211_asmdu_to_8023s
Date: Fri, 27 Nov 2009 10:18:20 +0100 [thread overview]
Message-ID: <1259313500.5428.2.camel@johannes.local> (raw)
In-Reply-To: <1259284014.13126.111.camel@debian>
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
On Fri, 2009-11-27 at 09:06 +0800, Zhu Yi wrote:
> > > + dev->stats.rx_packets++;
> > > + dev->stats.rx_bytes += skb->len;
> >
> > Shouldn't rx_packets be per sub-frame?
>
> Not very sure. Maybe it's one frame from the device's perspective? The
> original code does this so I didn't change the behavior. Should I?
Ah, yes, I remember now -- had been wondering about this before. What
does everybody else think?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-11-27 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 6:03 [RFC 1/2] wireless: add ieee80211_asmdu_to_8023s Zhu Yi
2009-11-26 6:03 ` [RFC 2/2] iwmc3200wifi: rx aggregation support Zhu Yi
2009-11-26 9:49 ` [RFC 1/2] wireless: add ieee80211_asmdu_to_8023s Johannes Berg
2009-11-27 1:06 ` Zhu Yi
2009-11-27 9:18 ` Johannes Berg [this message]
2009-11-26 10:05 ` Johannes Berg
2009-11-27 2:52 ` Zhu Yi
2009-11-27 9:20 ` Johannes Berg
2009-11-27 9:30 ` Zhu Yi
2009-11-27 9:33 ` Johannes Berg
2009-11-27 9:35 ` Johannes Berg
2009-11-30 2:34 ` Zhu Yi
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=1259313500.5428.2.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@intel.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).