From: Marcel Holtmann <holtmann@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iw: add kernel version checks for pending upstream kernel features
Date: Thu, 18 Sep 2008 22:43:23 +0200 [thread overview]
Message-ID: <1221770603.6782.35.camel@californication> (raw)
In-Reply-To: <1221758934.9262.89.camel@johannes.berg>
Hi Johannes,
> > if the numbers you are planning to use are stable, then please use the
> > above approach to just add the missing defines to it. Like adding a
> > compat.h file with
> >
> > #ifndef NL80211_ATTR_SUPPORTED_IFTYPES
> > #define NL80211_ATTR_SUPPORTED_IFTYPES boo
> > #endif
>
> Well, at that point I can also just copy nl80211.h from wireless-testing
> whenever I think the numbers will remain stable, no? And that doesn't
> work as-is anyway since nl80211.h uses an enum to define the numbers,
> not #defines.
it is possible to work around with just define the enum entries also as
defines. Netlink does this a lot. It is not pretty, but possible.
> I guess it's the lesser of all the evils. I'm not too fond of copying in
> the header file, it creates more work and doesn't make all that much
> sense, but all the other proposals take even more work, and as long as
> we don't change the numbers after putting things into wireless-testing
> we should be fine.
Simple speaking, yes :)
Regards
Marcel
next prev parent reply other threads:[~2008-09-18 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 14:35 [PATCH] iw: add kernel version checks for pending upstream kernel features John W. Linville
2008-09-18 15:13 ` Pavel Roskin
2008-09-18 15:41 ` Johannes Berg
2008-09-18 16:10 ` Pavel Roskin
2008-09-18 17:26 ` Marcel Holtmann
2008-09-18 17:28 ` Johannes Berg
2008-09-18 20:43 ` Marcel Holtmann [this message]
2008-09-18 19:19 ` Pavel Roskin
2008-09-19 1:25 ` John W. Linville
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=1221770603.6782.35.camel@californication \
--to=holtmann@linux.intel.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 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).