RE: [PATCH] mac80211: Fix addition of mesh configuration element

> -Original Message- > From: Johannes Berg [mailto:johan...@sipsolutions.net] > Sent: Monday, January 02, 2017 13:00 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; masashi.ho...@gmail.com > Subject: Re: [PATCH] mac80211: Fix addition of mesh configuration element

RE: iwlwifi support of 802.11k RRM (Radio Resource Mangament)

> -Original Message- > From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless- > ow...@vger.kernel.org] On Behalf Of Emmanuel Grumbach > Sent: Wednesday, March 02, 2016 14:53 > To: Stefan Feirer > Cc: linux-wireless > Subject: Re: iwlwifi support of 802.11k RRM (Radio Resource Ma

RE: [RFC V2 2/3] nl80211: add bss selection attribute to CONNECT command

> -Original Message- > From: Arend van Spriel [mailto:ar...@broadcom.com] > Sent: Wednesday, January 20, 2016 23:54 > To: Johannes Berg > Cc: linux-wireless; Peer, Ilan > Subject: Re: [RFC V2 2/3] nl80211: add bss selection attribute to CONNECT > command > &g

RE: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue

Hi Janusz, > -Original Message- > From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless- > ow...@vger.kernel.org] On Behalf Of Janusz Dziedzic > Sent: Sunday, June 28, 2015 00:49 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; chaitanya.m...@gmail.co

RE: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue

Hi Janusz, Any chance you can check if the attached patch fixes the issue you reported? Thanks in advance, Ilan. > -Original Message- > From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless- > ow...@vger.kernel.org] On Behalf Of Peer, Ilan > Sent: Tuesday, June

Re: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue

-Original Message- From: Krishna Chaitanya mailto:krishna%20chaitanya%20%3cchaitanya.m...@gmail.com%3e>> To: "Peer, Ilan" mailto:%22Peer,%20ilan%22%20%3cilan.p...@intel.com%3e>> Cc: Janusz Dziedzic mailto:janusz%20dziedzic%20%3cjanusz.dzied...@tieto.com

RE: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue

> >> > >> I suspect this is because of P2P_GO NoA? > >> Who should care about this direct probes tx when GO is not present? > >> > >> In case we didn't send direct probes - there is no problem and TC > >> works correctly > >> > > > > Interesting :) > > > > Any chance you can provide trace-cmd and s

RE: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue

> -Original Message- > From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless- > ow...@vger.kernel.org] On Behalf Of Janusz Dziedzic > Sent: Tuesday, June 23, 2015 11:51 > To: linux-wireless@vger.kernel.org > Cc: Peer, Ilan > Subject: AP + P2P_GO multichan

RE: [PATCH 1/2] mac80211_hwsim: Set VHT capabilities only for the 5.2 GHz band

Hi Ben, > -Original Message- > From: Ben Greear [mailto:gree...@candelatech.com] > Sent: Tuesday, April 07, 2015 19:08 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org > Subject: Re: [PATCH 1/2] mac80211_hwsim: Set VHT capabilities only for the > 5.2 GHz band >

RE: [PATCH v2] cfg80211: Stop calling crda if it is not responsive

> -Original Message- > From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless- > ow...@vger.kernel.org] On Behalf Of Johannes Berg > Sent: Wednesday, April 01, 2015 12:23 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; mcg...@suse.com > Subject: Re

RE: [PATCH 7/7] mac80211: Count correctly interface types

> Sent: Wednesday, April 01, 2015 12:16 > To: Johannes Berg > Cc: Janusz Dziedzic; Peer, Ilan; Grumbach, Emmanuel; linux- > wirel...@vger.kernel.org; Otcheretianski, Andrei > Subject: Re: [PATCH 7/7] mac80211: Count correctly interface types > > On 04/01/15 10:44, Johannes Berg wrote

RE: [PATCH v2] cfg80211: Stop calling crda if it is not responsive

> -Original Message- > From: Johannes Berg [mailto:johan...@sipsolutions.net] > Sent: Wednesday, April 01, 2015 11:51 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; mcg...@suse.com > Subject: Re: [PATCH v2] cfg80211: Stop calling crda if it is not responsive >

RE: [PATCH] cfg80211: Stop calling crda if it is not responsive

> -Original Message- > From: Johannes Berg [mailto:johan...@sipsolutions.net] > Sent: Monday, March 30, 2015 12:11 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; mcg...@suse.com > Subject: Re: [PATCH] cfg80211: Stop calling crda if it is not responsive > >

RE: [PATCH v10 3/3] cfg80211: Schedule timeout for all CRDA calls

Thanks :) Ilan. > -Original Message- > From: Luis R. Rodriguez [mailto:mcg...@suse.com] > Sent: Friday, March 06, 2015 00:55 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org > Subject: Re: [PATCH v10 3/3] cfg80211: Schedule timeout for all CRDA calls > > On

RE: [PATCH v9 2/3] cfg80211: Add API to change the indoor regulatory setting

> -Original Message- > From: Luis R. Rodriguez [mailto:mcg...@suse.com] > Sent: Monday, March 02, 2015 23:23 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; ArikX Nemtsov > Subject: Re: [PATCH v9 2/3] cfg80211: Add API to change the indoor > regulatory settin

RE: [PATCH v8 2/3] cfg80211: Add API to change the indoor regulatory setting

Hi Luis > -Original Message- > From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless- > ow...@vger.kernel.org] On Behalf Of Luis R. Rodriguez > Sent: Thursday, February 26, 2015 19:42 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; ArikX Nemtsov > S

RE: [PATCH v6 1/2] cfg80211: Add API to change the indoor regulatory setting

> -Original Message- > From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless- > ow...@vger.kernel.org] On Behalf Of Luis R. Rodriguez > Sent: Thursday, February 26, 2015 04:08 > To: Peer, Ilan > Cc: Jouni Malinen; linux-wireless@vger.kernel.org; ArikX Nem

RE: [PATCH v6 1/2] cfg80211: Add API to change the indoor regulatory setting

Hi Luis, > -Original Message- > From: Luis R. Rodriguez [mailto:mcg...@suse.com] > Sent: Tuesday, February 24, 2015 02:03 > To: Peer, Ilan; Jouni Malinen > Cc: linux-wireless@vger.kernel.org; ArikX Nemtsov > Subject: Re: [PATCH v6 1/2] cfg80211: Add API to change the i

RE: [PATCH v4 1/2] cfg80211: Add API to change the indoor regulatory setting

[mailto:mcg...@suse.com] > Sent: Friday, February 20, 2015 02:54 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; ArikX Nemtsov; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH v4 1/2] cfg80211: Add API to change the indoor > regulatory setting > > Wider community:

RE: [PATCH v4 1/2] cfg80211: Add API to change the indoor regulatory setting

Hi Luis, > > > > This differs from the country setting that would potentially require > > user space interaction and might invoke more complex flows. The flow > > in this case is immediate, and does not require the somewhat complex > > handling of country settings (it even complicates the flow > >

RE: [PATCH v4 1/2] cfg80211: Add API to change the indoor regulatory setting

Hi Luis, > -Original Message- > From: Luis R. Rodriguez [mailto:mcg...@suse.com] > Sent: Saturday, February 07, 2015 01:58 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; ArikX Nemtsov > Subject: Re: [PATCH v4 1/2] cfg80211: Add API to change the indoor > regul

RE: [PATCH v2 2/2] cfg80211: Schedule timeout for all CRDA calls

> -Original Message- > From: Johannes Berg [mailto:johan...@sipsolutions.net] > Sent: Tuesday, January 06, 2015 12:59 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; mcg...@suse.com > Subject: Re: [PATCH v2 2/2] cfg80211: Schedule timeout for all CRDA calls >

RE: [PATCH 1/2] cfg80211: Add API to change the indoor regulatory setting

> -Original Message- > From: Johannes Berg [mailto:johan...@sipsolutions.net] > Sent: Tuesday, January 06, 2015 12:11 > To: Peer, Ilan > Cc: linux-wireless@vger.kernel.org; mcg...@suse.com; ArikX Nemtsov > Subject: Re: [PATCH 1/2] cfg80211: Add API to change the

RE: P2P_DEVICE support in Android KitKat

Hi Arend, We've encountered this issue in the past, and resolved it by passing the wpa_supplicant a P2P specific configuration file using the -m option. Try using -m but do not populate it with any network blocks that are not P2P groups. Hope this helps, Ilan. > -Original Message- > F