From: Olivier Galibert <galibert@pobox.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Hack inc." <linux-kernel@vger.kernel.org>
Subject: Re: Is that an acceptable interface change?
Date: Mon, 6 Mar 2006 16:50:21 +0100 [thread overview]
Message-ID: <20060306155021.GA23513@dspnet.fr.eu.org> (raw)
In-Reply-To: <1141631568.4084.2.camel@laptopd505.fenrus.org>
On Mon, Mar 06, 2006 at 08:52:48AM +0100, Arjan van de Ven wrote:
> On Mon, 2006-03-06 at 02:17 +0100, Olivier Galibert wrote:
> > I'm looking at the changes in the asound.h file, and especially at
> > commit 512bbd6a85230f16389f0dd51925472e72fc8a91, and I've been
> > wondering if it's acceptable compatibility-wise. All the structures
> > passed through ioctl (and ALSA is 100% ioctl) have been renamed from
> > sndrv_* to snd_*. That breaks source compatibility but not binary
> > compatibility.
>
> only if you are "stupid" enough to use kernel headers in your userspace!
> Which you shouldn't do normally
Does that mean it is the responsability of whoever packages the
headers for userspace consumption to rename the structs back? Or that
every application should come with its own copy of the kernel headers
it may need and be ready for massive source-level breakage when
rebasing?
I'm just trying to understand if we care about source compatibility
for userspace or not.
OG.
next prev parent reply other threads:[~2006-03-06 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 1:17 Olivier Galibert
2006-03-06 7:52 ` Arjan van de Ven
2006-03-06 15:50 ` Olivier Galibert [this message]
2006-03-06 15:55 ` Jesper Juhl
2006-03-06 16:15 ` Olivier Galibert
2006-03-06 16:20 ` Jesper Juhl
2006-03-06 16:25 ` Randy.Dunlap
2006-03-06 17:00 ` Paul Jackson
2006-03-06 17:23 ` Christopher Friesen
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=20060306155021.GA23513@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome