mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Marcus Metzler <mocm@metzlerbros.de>,
	Christoph Hellwig <hch@infradead.org>,
	mocm@mocm.de, Michael Hunold <hunold@convergence.de>,
	Sam Ravnborg <sam@ravnborg.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DVB Include files
Date: 26 Jun 2003 00:08:02 +0100	[thread overview]
Message-ID: <1056582481.1998.20.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030625202312.GG1770@wohnheim.fh-wedel.de>

On Mer, 2003-06-25 at 21:23, Jörn Engel wrote:
> So you don't recompile, but you still changed the magic ioctl numbers
> from 17 to 47 and from 18 to 48.  Old binaries don't work any more,
> even though the same semantics are still present.  That is an
> incompatible change in my book.
> 
> Worse if there is a new semantic for 17 or 18, in that case the old
> binaries may break randomly, depending on kernel version.

Sure but you keep old ones around once its stable. This is a completely
pointless conversation to have before 2.6.0-test kernels. There isnt a
stable in kernel dvb api yet because its not been shipped in a stable
kernel.

(Although I'd note the api has been as stable if not more stable than
some in kernel stuff 8))


  parent reply	other threads:[~2003-06-25 22:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 15:06 Sam Ravnborg
2003-06-25 15:08 ` Christoph Hellwig
2003-06-25 15:42   ` Sam Ravnborg
2003-06-25 16:17     ` Michael Hunold
2003-06-25 16:49       ` Marcus Metzler
2003-06-25 16:55         ` Christoph Hellwig
2003-06-25 17:13           ` Marcus Metzler
2003-06-25 17:16             ` Christoph Hellwig
2003-06-25 17:22               ` Marcus Metzler
2003-06-25 17:24                 ` Christoph Hellwig
2003-06-25 17:30                   ` Marcus Metzler
2003-06-25 17:50                     ` Christoph Hellwig
2003-06-25 18:09                       ` Marcus Metzler
2003-06-25 18:15                         ` Christoph Hellwig
2003-06-25 18:43                           ` Marcus Metzler
2003-06-25 19:42                             ` Jörn Engel
2003-06-25 20:09                               ` Marcus Metzler
2003-06-25 20:23                                 ` Jörn Engel
2003-06-25 20:48                                   ` Marcus Metzler
2003-06-25 21:03                                     ` Christoph Hellwig
2003-06-25 21:38                                       ` Marcus Metzler
2003-06-26 13:54                                         ` Henning P. Schmiedehausen
2003-06-25 23:08                                   ` Alan Cox [this message]
2003-06-26  8:18                                     ` Michael Hunold
2003-06-26  8:24                                       ` Christoph Hellwig
2003-06-26 13:20                                         ` Johannes Stezenbach
2003-06-25 21:03                             ` Christoph Hellwig
2003-06-25 17:27           ` Jörn Engel
2003-06-25 17:49             ` Christoph Hellwig

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=1056582481.1998.20.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=hch@infradead.org \
    --cc=hunold@convergence.de \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mocm@metzlerbros.de \
    --cc=mocm@mocm.de \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®