From: Ben Greear <greearb@candelatech.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"open list:ATHEROS ATH5K WIR..." <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: skb->priority magic values as part of UAPI headers?
Date: Fri, 14 Mar 2014 08:56:00 -0700 [thread overview]
Message-ID: <53232690.5040603@candelatech.com> (raw)
In-Reply-To: <CAGXE3d9s-FjVWF-y1n8Zrgzz3YZJ-yNnEQNoVeMfZYJRfbdXTA@mail.gmail.com>
On 03/14/2014 02:26 AM, Helmut Schaa wrote:
> On Thu, Mar 13, 2014 at 6:04 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> While browsing through net/wireless/util.c::cfg80211_classify8021d() I
>> stumbled upon the "magic values" range 256 to 263, should not those be
>> made part of some sort of user-space API header file, just so if
>> things need to be changed, they suddenly do not break?
>
> I stumbled over that some time ago as well [1].
> The question is if this is required at all anymore or if it could just
> be removed.
> Helmut
I use it to easily poke user-space generated packets into specific
transmit queues on the NIC. Please do not remove it.
Thanks,
Ben
>
> [1] http://comments.gmane.org/gmane.linux.kernel.wireless.general/82689
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-03-14 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 5:04 skb->priority magic values as part of UAPI headers? Florian Fainelli
2014-03-14 9:26 ` Helmut Schaa
2014-03-14 15:56 ` Ben Greear [this message]
2014-03-14 19:28 ` Florian Fainelli
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=53232690.5040603@candelatech.com \
--to=greearb@candelatech.com \
--cc=f.fainelli@gmail.com \
--cc=helmut.schaa@googlemail.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.