linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Denton Gentry <denton.gentry@gmail.com>
Subject: Re: [RFC/RFT 2/2] ath10k: fix Rx aggregation reordering
Date: Mon, 30 Jun 2014 10:59:44 +0300	[thread overview]
Message-ID: <8738emsu8f.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQ=n-NGGbJ9tJ+Q=7Lhnd2XxWTWRZLBV-q1gDoc7bFitrA@mail.gmail.com> (Michal Kazior's message of "Mon, 30 Jun 2014 07:41:07 +0200")

Michal Kazior <michal.kazior@tieto.com> writes:

> On 27 June 2014 16:17, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>> --- a/drivers/net/wireless/ath/ath10k/htt_rx.c
>>> +++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
>>> @@ -21,6 +21,7 @@
>>>  #include "txrx.h"
>>>  #include "debug.h"
>>>  #include "trace.h"
>>> +#include "mac.h"
>>
>> Why this? At least from a quick search I didn't see any reason to add this.
>
> ath10k_get_arvif()

Ah, ok. BTW, in the future we should rename it to ath10k_mac_get_arvif()
to make it clear it's coming from mac.c.

-- 
Kalle Valo

  reply	other threads:[~2014-06-30  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27  9:06 [RFC/RFT 0/2] mac80211/ath10k: fix Rx reordering Michal Kazior
2014-06-27  9:06 ` [RFC/RFT 1/2] mac80211: add support for Rx reordering offloading Michal Kazior
2014-07-08  7:10   ` Johannes Berg
2014-07-14 13:18     ` Michal Kazior
2014-06-27  9:06 ` [RFC/RFT 2/2] ath10k: fix Rx aggregation reordering Michal Kazior
2014-06-27 14:17   ` Kalle Valo
2014-06-30  5:41     ` Michal Kazior
2014-06-30  7:59       ` Kalle Valo [this message]
2014-06-27 18:17 ` [RFC/RFT 0/2] mac80211/ath10k: fix Rx reordering Denton Gentry

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=8738emsu8f.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=denton.gentry@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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).