Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith <m.sujith@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, mcgrof@gmail.com,
	jouni.malinen@atheros.com
Subject: Re: [RFC] Handle Channel Switch Announcement
Date: Thu, 18 Dec 2008 07:06:48 +0530	[thread overview]
Message-ID: <18761.43312.692142.691266@localhost.localdomain> (raw)
In-Reply-To: <1229537272.4268.7.camel@localhost>

Johannes Berg wrote:
> I agree with Jouni, this is probably not a good idea, especially since
> this flag would be shared between hardware for those drivers that have
> the channel structs allocated statically. We should probably just stick
> a struct ieee80211_channel *switch_from; pointer somewhere into the
> sdata struct or so.

Ok.

> I think I'd like to have them dropped to monitor for !station here,
> instead of silently in the processing function.

Ok.

> That should probably be removed or be more specific & protected by some
> debug #ifdef.

That just slipped through, I'll remove it.

> Can you rebase this on top of Kalle's patch that adds the "stop reasons"
> for each queue? As it is now, the driver could wake up the queues again
> if one was full.

Ok, I will.

Sujith

      reply	other threads:[~2008-12-18  1:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 14:55 [RFC] Handle Channel Switch Announcement Sujith
2008-12-17 16:20 ` Jouni Malinen
2008-12-18  1:32   ` Sujith
2008-12-18  3:59     ` Sujith
2008-12-18  7:05     ` Jouni Malinen
2008-12-18  7:18       ` Jouni Malinen
2008-12-17 18:07 ` Johannes Berg
2008-12-18  1:36   ` Sujith [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=18761.43312.692142.691266@localhost.localdomain \
    --to=m.sujith@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=jouni.malinen@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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