All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Linux Wireless List" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wext: include wireless event id when it has a size problem
Date: Wed, 5 Sep 2012 18:21:48 +0200	[thread overview]
Message-ID: <50477C1C.6020209@broadcom.com> (raw)
In-Reply-To: <1346854421.4364.21.camel@jlt4.sipsolutions.net>

On 09/05/2012 04:13 PM, Johannes Berg wrote:
> On Fri, 2012-08-24 at 14:43 +0200, Arend van Spriel wrote:
>> The wext code checks is the event data is within size limits.
>> When this check fails a message is logged with violating size.
>> This patch adds the event id to put us on the right track for
>> resolving that violation.
>>
>> Reviewed-by: Hante Meuleman <meuleman@broadcom.com>
>> Signed-off-by: Arend van Spriel <arend@broadcom.com>
>> ---
>> Maybe wext is not popular, but I found the change helpful debugging
>> so others may benefit from it. Still some wireless apps default to
>> it, eg. wpa_supplicant.
>
> I don't even want to know what you're debugging, but I applied it
> anyway.
>
> FWIW, wext isn't just "not popular", it's "pretty much dead" :-)
>
> johannes
>
>

We got the "Wireless Event too big" message and were wondering what 
event from our driver was causing it. I agree wext is pretty much dead 
although wpa_supplicant still defaults to that driver. At least in most 
distro's it seems to be so.

Gr. AvS


      reply	other threads:[~2012-09-05 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 12:43 [PATCH] wext: include wireless event id when it has a size problem Arend van Spriel
2012-09-05 14:13 ` Johannes Berg
2012-09-05 16:21   ` Arend van Spriel [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=50477C1C.6020209@broadcom.com \
    --to=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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.