From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: cfg80211 API for channels/bitrates, mac80211 and driver conversion
Date: Fri, 28 Dec 2007 14:01:03 -0800 (PST) [thread overview]
Message-ID: <20071228.140103.159573237.davem@davemloft.net> (raw)
In-Reply-To: <1198878633.4172.19.camel@johannes.berg>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Fri, 28 Dec 2007 22:50:33 +0100
> include/net/wireless.h | 168 ++++++++++
Are the datastructures in this file the ones that go over
netlink and thus userland sees?
If so, please move the definitions to some file under include/linux,
as a convention we do not put userland API definitions into files
under include/net, that's why there is no include/net/Kbuild file.
next prev parent reply other threads:[~2007-12-28 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 21:50 cfg80211 API for channels/bitrates, mac80211 and driver conversion Johannes Berg
2007-12-28 22:01 ` David Miller [this message]
2007-12-28 22:05 ` Johannes Berg
2007-12-28 22:21 ` David Miller
2007-12-28 22:10 ` Michael Buesch
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=20071228.140103.159573237.davem@davemloft.net \
--to=davem@davemloft.net \
--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 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).