linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: <ath6kl-devel@qca.qualcomm.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath6kl: Set HT caps when an interface is added
Date: Fri, 16 Nov 2012 19:38:09 +0530	[thread overview]
Message-ID: <50A648C9.6030108@qca.qualcomm.com> (raw)
In-Reply-To: <50A62400.2020603@qca.qualcomm.com>

Hi Kalle,

On Friday 16 November 2012 05:01 PM, Kalle Valo wrote:
> Hi,
>
> On 10/22/2012 08:25 AM, Mohammed Shafi Shajakhan wrote:
>> On Sunday 21 October 2012 03:28 PM, Kalle Valo wrote:
>>> Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com> writes:
>>>
>>>> From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
>>>>
>>>> Set HT capabilites when a vif is added (based on ht_supported
>>>> advertized is 'true'). ath6kl_set_htcap
>>>> seems to be called when an AP vif is added but not so in
>>>> other vifs. Fix this.
>>>>
>>>> Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
>>>
>>> This was found during code review, right? Or does it fix a real bug?
>>
>> yes this was based on code review, would soon come with some test
>> results with multivif.
>
> I'm not sure what was the conclusion, is this safe to apply?

Sorry i missed this, yeah will confirm it soon with a basic test and let 
you know. Please don't apply till that. thanks for your patience :)

>
> Kalle
>


-- 
thanks,
shafi



      reply	other threads:[~2012-11-16 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 15:52 [PATCH] ath6kl: Set HT caps when an interface is added Mohammed Shafi Shajakhan
2012-10-21  9:58 ` Kalle Valo
2012-10-22  5:25   ` Mohammed Shafi Shajakhan
2012-11-16 11:31     ` Kalle Valo
2012-11-16 14:08       ` Mohammed Shafi Shajakhan [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=50A648C9.6030108@qca.qualcomm.com \
    --to=mohammed@qca.qualcomm.com \
    --cc=ath6kl-devel@qca.qualcomm.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).