public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] rfkill: prep for rfkill API changes
Date: Mon, 6 Jul 2009 12:58:05 -0300	[thread overview]
Message-ID: <20090706155805.GD753@khazad-dum.debian.net> (raw)
In-Reply-To: <1246801098.4411.5.camel@johannes.local>

On Sun, 05 Jul 2009, Johannes Berg wrote:
> On Sun, 2009-07-05 at 10:24 -0300, Henrique de Moraes Holschuh wrote:
> > This is good, but not complete.  Changes to the API that don't change the
> > size (or those which reduces it) are a problem: they are impossible with a
> > schema that detects API version by the size alone.
> 
> Umm, no, we can also add operations as required already.

Yeah, I know.  What we can't do is to change the current ones, or drop them.

> _subtlety_ involved in actually doing a size change, nothing more. A
> real event version is _not_ necessary at all. In fact, I would argue
> that basing _anything_ on the "version" rather than the "feature set" is
> useless.

IMO version can tell you the supported feature set, but one could use a
feature set bitmap as well if one wanted.  Anyway, if you guys deem the
current way good enough, I am fine with it.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2009-07-06 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 12:51 [PATCH] rfkill: prep for rfkill API changes Johannes Berg
2009-07-05 13:24 ` Henrique de Moraes Holschuh
2009-07-05 13:38   ` Johannes Berg
2009-07-06 15:58     ` Henrique de Moraes Holschuh [this message]
2009-07-05 17:29 ` Marcel Holtmann

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=20090706155805.GD753@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --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