From: "Piotr Haber" <phaber@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] cfg80211: advertise extended capabilities to userspace
Date: Wed, 27 Feb 2013 13:48:07 +0100 [thread overview]
Message-ID: <512E0087.4070006@broadcom.com> (raw)
In-Reply-To: <1361968360.8172.5.camel@jlt4.sipsolutions.net>
On 02/27/13 13:32, Johannes Berg wrote:
> On Wed, 2013-02-27 at 13:30 +0100, Piotr Haber wrote:
>
>> seems like this patch pushed wiphy info length over the limit
>> for dual band devices.
>> So userspace cannot get any info about phy capabilities.
>
> Yeah ... was it this patch? I did revert some others, but I guess it
> depends.
did not bisect, but that was the last big thing added there
>> I know there is a patch for nl80211 and iw to allow splitting of this info,
>> but it is not in 3.8
>> Should we not revert it for stable then?
>
> Yeah we can revert this too, a la the patches already in to remove TCP
> wakeup and radar info. What kernel are you testing?
>
i have one built from wireless-testing master-2013-02-19
next prev parent reply other threads:[~2013-02-27 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 14:01 [PATCH 1/2] cfg80211: advertise extended capabilities to userspace Johannes Berg
2013-02-12 14:01 ` [PATCH 2/2] mac80211: advertise operating mode notification capability Johannes Berg
2013-02-14 20:02 ` [PATCH 1/2] cfg80211: advertise extended capabilities to userspace Johannes Berg
2013-02-27 12:30 ` Piotr Haber
2013-02-27 12:32 ` Johannes Berg
2013-02-27 12:48 ` Piotr Haber [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-11 15:25 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=512E0087.4070006@broadcom.com \
--to=phaber@broadcom.com \
--cc=johannes@sipsolutions.net \
--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.