All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 2/2] ath10k: don't advertise we want monitor vif
Date: Fri, 26 Apr 2013 10:37:43 +0300	[thread overview]
Message-ID: <8738udvj20.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20855.64445.611540.12468@gargle.gargle.HOWL> (Sujith Manoharan's message of "Wed, 24 Apr 2013 21:05:25 +0530")

Hi,

Sujith Manoharan <sujith@msujith.org> writes:

> Michal Kazior wrote:
>
>> Considering how "stable" monitor mode is perhaps we should start
>> monitor vdev only when there's the monitor vif present? (right now
>> we can start it without the vdev). If so then we drop this patch.
>> And we probably also should forbid packet injection, at least until
>> FW gets this sorted out.
>
> Well, the requirement is that we *need* a VDEV for monitor mode and
> this is precisely this flag is for. So I don't quite see how removing it
> fixes anything ?

So what's the conclusion? What should we do with this patchset?

-- 
Kalle Valo

      reply	other threads:[~2013-04-26  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 10:17 [ath9k-devel] [PATCH 0/2] ath10k: monitor mode fixes Michal Kazior
2013-04-24 10:17 ` [ath9k-devel] [PATCH 1/2] ath10k: avoid null dereference on vif Michal Kazior
2013-04-24 10:17 ` [ath9k-devel] [PATCH 2/2] ath10k: don't advertise we want monitor vif Michal Kazior
2013-04-24 11:36   ` Sujith Manoharan
2013-04-24 12:18     ` Michal Kazior
2013-04-24 15:35       ` Sujith Manoharan
2013-04-26  7:37         ` 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=8738udvj20.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath9k-devel@lists.ath9k.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 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.