All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: "Peer, Ilan" <ilan.peer@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"chaitanya.mgit@gmail.com" <chaitanya.mgit@gmail.com>
Subject: Re: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue
Date: Thu, 02 Jul 2015 13:39:28 +0200	[thread overview]
Message-ID: <1435837168.2285.8.camel@sipsolutions.net> (raw)
In-Reply-To: <CALhHN=ojLBA1AFGz=atjJhv+fJAr-Rkhd0cgYpma_4Rx+HYOaw@mail.gmail.com> (sfid-20150702_114406_759616_5CDED4CB)

On Thu, 2015-07-02 at 11:44 +0200, Janusz Dziedzic wrote:
> 
> > The issue above can probably easily fixed by doing the BSS update 
> > after
> > the "direct probe responded" though, no? Like this:
> > https://p.sipsolutions.net/67f9212f0f9f3642.txt
> > 
> This was my first idea, but in such case I suspect we will send
> another direct probe while  bss->proberesp_ies will be not set and
> ieee80211_probe_auth() will send second probe_req?
> 

But why would it not be set? We do rely on ieee80211_rx_bss_info()
setting it, after all.

johannes

  reply	other threads:[~2015-07-02 11:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  8:50 AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue Janusz Dziedzic
2015-06-23 11:11 ` Peer, Ilan
2015-06-23 11:29   ` Krishna Chaitanya
2015-06-23 11:55     ` Peer, Ilan
2015-06-23 12:04       ` Krishna Chaitanya
2015-06-23 18:00         ` Peer, Ilan
2015-06-24 12:20           ` Peer, Ilan
2015-06-27 21:49             ` Janusz Dziedzic
2015-06-27 22:03               ` Janusz Dziedzic
2015-06-28  8:36               ` Peer, Ilan
2015-07-02  7:27               ` Johannes Berg
2015-07-02  9:02                 ` Krishna Chaitanya
2015-07-02 11:38                   ` Johannes Berg
2015-07-02 11:49                     ` Krishna Chaitanya
2015-07-02  9:44                 ` Janusz Dziedzic
2015-07-02 11:39                   ` Johannes Berg [this message]
2015-07-02 11:50                     ` Krishna Chaitanya
2015-07-02 12:01                       ` Johannes Berg
2015-07-02 12:13                         ` Krishna Chaitanya
2015-07-02 12:37                           ` Johannes Berg

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=1435837168.2285.8.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=chaitanya.mgit@gmail.com \
    --cc=ilan.peer@intel.com \
    --cc=janusz.dziedzic@tieto.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 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.