netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	netdev@vger.kernel.org, Jouni Malinen <jkm@devicescape.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: 802.11 headers
Date: Thu, 17 Aug 2006 08:43:33 -0400	[thread overview]
Message-ID: <20060817124327.GA17771@tuxdriver.com> (raw)
In-Reply-To: <20060817143443.77ede2e5@griffin.suse.cz>

On Thu, Aug 17, 2006 at 02:34:43PM +0200, Jiri Benc wrote:
> On Thu, 17 Aug 2006 09:48:19 +0200, Johannes Berg wrote:

> > Or put another way, my suggestions:
> >  - put all in-kernel API (for drivers) into net/d80211.h
> >  - put stuff defined in the IEEE 802.11 specification series into
> >    linux/ieee80211.h, make user-visible (headers-y in Kbuild!). This
> >    serves just as a reference. It's not really necessary that the kernel
> >    ships this, but we need it in the kernel and probably won't be
> >    pulling it from some other source. Besides, I wouldn't know where
> >    else to maintain it.
> >  - radiotap simply moves to linux/ and gets to be userland-visible. Of
> >    course, d80211 should actually start using it too ;)
> >  - all the other userland stuff seems to be configuration related and
> >    hence moves over to linux/nl80211.h
> > 
> > Comments?
> 
> I like this proposal.

I second that.

John
-- 
John W. Linville
linville@tuxdriver.com

      reply	other threads:[~2006-08-17 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17  7:48 802.11 headers Johannes Berg
2006-08-17 12:34 ` Jiri Benc
2006-08-17 12:43   ` John W. Linville [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=20060817124327.GA17771@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dwmw2@infradead.org \
    --cc=jbenc@suse.cz \
    --cc=jkm@devicescape.com \
    --cc=johannes@sipsolutions.net \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).