linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Inaky Perez-Gonzalez
	<public-inaky-VuQAYsv1563Yd54FQh9/CA@hugh.gmane.org>,
	Stephen Hemminger
	<public-stephen.hemminger-ZtmgI6mnKB3QT0dZR+AlfA@hugh.gmane.org>,
	public-wimax-BPSAo7wm5JOHVYUYWc+uSQ@hugh.gmane.org,
	public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org,
	public-netdev-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org,
	public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org
Subject: Re: [ANN] WiMAX stack and drivers for Intel WiMAX Link 5050
Date: Wed, 9 Apr 2008 11:09:24 -0700	[thread overview]
Message-ID: <200804091109.25265.inaky@linux.intel.com> (raw)
In-Reply-To: <871w5fpnhs.fsf@basil.nowhere.org>




On Tuesday 08 April 2008, Andi Kleen wrote:

> > version: I anticipate the wimax API exported to user space is
> > going to undergo a lot of changes while we all agree on what
> > is the best interface. Because things might break, I want to
> > make sure user space stuff can detect that and fail cleanly. 
> > Hence the versioning. 
> 
> It's still a bad way to do that (I agree with Stephen on that).
> Was also always a mess on wireless.
> 
> If you don't want expandable TLAs another better alternative to 
> versions is ext2 style compatible/incompatible feature bitmaps.

Ain't that another way of saying versions? Sorry guys, but I am 
having a hard time understanding how the alternatives are better.

Expandable TLAs are fine, until we need to change the meaning of
an existing field/value. Then there is no way to change it without 
breaking existing code other than create a new message. And then 
we have a mess like wireless again. 

With simple versioning, we just bump up the major number and break.
In user space, the libwimax shim library would take care of  hiding
this for the user if so is needed.

-- 
Inaky




  parent reply	other threads:[~2008-04-09 20:31 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 [this message]
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
  -- 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=200804091109.25265.inaky@linux.intel.com \
    --to=inaky@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=public-inaky-VuQAYsv1563Yd54FQh9/CA@hugh.gmane.org \
    --cc=public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
    --cc=public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
    --cc=public-netdev-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
    --cc=public-stephen.hemminger-ZtmgI6mnKB3QT0dZR+AlfA@hugh.gmane.org \
    --cc=public-wimax-BPSAo7wm5JOHVYUYWc+uSQ@hugh.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).