All of lore.kernel.org
 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>,
	Denton Gentry <denton.gentry@gmail.com>
Subject: Re: [PATCH v3] ath10k: fix Rx aggregation reordering
Date: Wed, 23 Jul 2014 19:20:46 +0300	[thread overview]
Message-ID: <87fvhst5b5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQng1xwLEbwfQ6P-T=VWYby529jFZ=duTH6hC=HzMW9Y=w@mail.gmail.com> (Michal Kazior's message of "Wed, 23 Jul 2014 11:50:02 +0200")

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

>> The mac80211 patches are in mac80211-next, but I can only apply this one
>> only once they are in wireless-next.
>>
>> Also the other thing is that 3.17 merge window is very close. I might be
>> able to squeeze this in but there's the risk that this patch hasn't
>> received enough testing from being in ath.git. How safe (or risky) is
>> this patch? If we push this to 3.17, we could try to fix regressions in
>> -rc releases but that's always more difficult than waiting for 3.18.
>
> I think it should be fairly safe. The stalls I've observed don't make
> it worse than it is without Rx reordering.
>
> But! I need to re-spin this patch since there's an endianess bug with
> info0 being treated as __le32 while its __le16.

Ok, let's try to get the new version of this patch to 3.17, if at all
possible. But if there are any regressions, please let me know ASAP so
that we can quickly fix it and push the fix to -rc releases.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-07-23 16:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 10:17 [PATCH v2] ath10k: fix Rx aggregation reordering Michal Kazior
2014-07-16 10:17 ` Michal Kazior
2014-07-16 11:19 ` [PATCH v3] " Michal Kazior
2014-07-16 11:19   ` Michal Kazior
2014-07-16 11:38   ` Varka Bhadram
2014-07-16 11:38     ` Varka Bhadram
2014-07-16 12:35     ` Michal Kazior
2014-07-16 12:35       ` Michal Kazior
2014-07-16 12:41       ` Michal Kazior
2014-07-16 12:41         ` Michal Kazior
2014-07-18 12:41         ` Kalle Valo
2014-07-18 12:41           ` Kalle Valo
2014-07-22 18:37   ` Kalle Valo
2014-07-23  9:50     ` Michal Kazior
2014-07-23 16:20       ` Kalle Valo [this message]
2014-07-23 10:20   ` [PATCH v4] " Michal Kazior
2014-07-23 10:20     ` Michal Kazior
2014-07-25  8:18     ` Kalle Valo
2014-07-25  8:18       ` Kalle Valo

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=87fvhst5b5.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=denton.gentry@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.