linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: "linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>, Cathy Luo <cluo@marvell.com>,
	Avinash Patil <patila@marvell.com>
Subject: Re: [PATCH] mwifiex: fix a bug in Rx multiport aggregation logic
Date: Fri, 13 Mar 2015 16:29:14 +0200	[thread overview]
Message-ID: <87k2ylq8cl.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5FF020A1CFFEEC49BD1E09530C4FF5951B16A0745C@SC-VEXCH1.marvell.com> (Amitkumar Karwar's message of "Thu, 12 Mar 2015 07:07:49 -0700")

Amitkumar Karwar <akarwar@marvell.com> writes:

>> -----Original Message-----
>> From: Amitkumar Karwar [mailto:akarwar@marvell.com]
>> Sent: Thursday, March 12, 2015 1:09 PM
>> To: linux-wireless@vger.kernel.org
>> Cc: Cathy Luo; Avinash Patil; Amitkumar Karwar
>> Subject: [PATCH] mwifiex: fix a bug in Rx multiport aggregation logic
>> 
>> From: Cathy Luo <cluo@marvell.com>
>> 
>> It's been observed Rx aggregated packets are always followed by a
>> single Rx packet. This patch improves our logic to add that extra
>> packet in next aggregation.
>> 
>> Signed-off-by: Cathy Luo <cluo@marvell.com>
>> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
>> ---
>
> Please ignore this patch. This is same as "[PATCH 1/3] mwifiex: fix 
> a bug..." sent separately.

Ok, I dropped this patch.

-- 
Kalle Valo

      reply	other threads:[~2015-03-13 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  7:38 [PATCH] mwifiex: fix a bug in Rx multiport aggregation logic Amitkumar Karwar
2015-03-12  7:38 ` [PATCH 2/3] mwifiex: Add support for auto ARP in mwifiex Amitkumar Karwar
2015-03-16 16:05   ` [2/3] " Kalle Valo
2015-03-12  7:38 ` [PATCH 3/3] mwifiex: use del_timer variant in interrupt context Amitkumar Karwar
2015-03-12 14:07 ` [PATCH] mwifiex: fix a bug in Rx multiport aggregation logic Amitkumar Karwar
2015-03-13 14:29   ` Kalle Valo [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=87k2ylq8cl.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=patila@marvell.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).