From: Stephen Hemminger <stephen.hemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
To: Inaky Perez-Gonzalez <inaky-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: wimax-BPSAo7wm5JOHVYUYWc+uSQ@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [ANN] WiMAX stack and drivers for Intel WiMAX Link 5050
Date: Tue, 8 Apr 2008 14:04:03 -0500 [thread overview]
Message-ID: <20080408140403.3e7191bb@speedy> (raw)
In-Reply-To: <200804011107.38563.inaky-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Looking at the kernel/user interface: wimax-tools-1.1/lib/op-open.c
This API is repeating the mistake of the old Linux Wireless API. It is putting version
checks between kernel and library and this is a maintenance nightmare. Linux
API's are not COM. Versioning is a mistake. Use a TLA api like netlink so it
can be extensible without version handshake.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-04-08 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 18:07 [ANN] WiMAX stack and drivers for Intel WiMAX Link 5050 Inaky Perez-Gonzalez
[not found] ` <200804011107.38563.inaky-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2008-04-01 18:18 ` Stephen Hemminger
2008-04-01 18:33 ` Inaky Perez-Gonzalez
2008-04-08 15:13 ` Stephen Hemminger
2008-04-08 19:04 ` Stephen Hemminger [this message]
2008-04-08 18:56 ` Stephen Hemminger
2008-04-08 19:44 ` Marcel Holtmann
2008-04-08 20:59 ` Inaky Perez-Gonzalez
2008-04-09 6:10 ` Andi Kleen
[not found] ` <871w5fpnhs.fsf@basil.nowhere.org>
[not found] ` <200804091109.25265.inaky@linux.intel.com>
2008-04-09 20:31 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2008-04-08 18:57 jayant
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=20080408140403.3e7191bb@speedy \
--to=stephen.hemminger-ztmgi6mnkb3qt0dzr+alfa@public.gmane.org \
--cc=inaky-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wimax-BPSAo7wm5JOHVYUYWc+uSQ@public.gmane.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).