linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Cc: wimax@linuxwimax.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.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@linux.intel.com>

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.

  parent reply	other threads:[~2008-04-08 19:04 UTC|newest]

Thread overview: 17+ 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
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 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
2008-04-09  8:05       ` Holger Schurig
2008-04-09  8:23         ` Philip Craig
2008-04-09 18:09       ` Inaky Perez-Gonzalez
2008-04-09 20:31         ` Andi Kleen
2008-04-09  7:59     ` Holger Schurig
2008-04-09 18:12       ` Inaky Perez-Gonzalez
2008-04-09 20:49         ` Chr
2008-04-08 19:04 ` Stephen Hemminger [this message]
  -- 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@vyatta.com \
    --cc=inaky@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wimax@linuxwimax.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).