ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2 0/2] ath10k: improve set_bitrate_mask
Date: Wed, 1 Apr 2015 20:34:20 +0300	[thread overview]
Message-ID: <874mozycpv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1427798961-7334-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Tue, 31 Mar 2015 10:49:19 +0000")

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

> This makes set_bitrate_mask more flexible by
> allowing more than applying simple single rate or
> max nss limits.
>
> This still isn't ideal and VHT MCSs can't be set
> separately (only a few range-options are allowed).
>
> v2:
>  * fix ouf-of-bounds
>  * rebased to master branch + multi-channel patches
>
> This will not apply cleanly without multi-channel
> support and conflict resolution will be
> non-trivial.
>
>
> Michal Kazior (2):
>   ath10k: clean up set_bitrate_mask handling

Thanks, this patch applied.

>   ath10k: implement more versatile set_bitrate_mask

This patch dropped as requested.

-- 
Kalle Valo

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

      parent reply	other threads:[~2015-04-01 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 10:49 [PATCH v2 0/2] ath10k: improve set_bitrate_mask Michal Kazior
2015-03-31 10:49 ` [PATCH v2 1/2] ath10k: clean up set_bitrate_mask handling Michal Kazior
2015-03-31 10:49 ` [PATCH v2 2/2] ath10k: implement more versatile set_bitrate_mask Michal Kazior
2015-04-01 12:38   ` Michal Kazior
2015-04-01 17:09     ` Kalle Valo
2015-04-01 17:34 ` 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=874mozycpv.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --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