From: Carlos O'Donell <carlos@redhat.com>
To: Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
Elichai Turkel <elichai.turkel@gmail.com>,
Florian Weimer <fweimer@redhat.com>
Cc: nd <nd@arm.com>, Christian Brauner <christian.brauner@ubuntu.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Continuing the UAPI split
Date: Thu, 7 Nov 2019 13:05:19 -0500 [thread overview]
Message-ID: <086ffddf-553f-453d-a046-4d5e6abead21@redhat.com> (raw)
In-Reply-To: <facb4d0d-4e20-41f0-4c01-b210c677c24c@arm.com>
On 11/7/19 11:21 AM, Szabolcs Nagy wrote:
>> Or just giving up and telling users they can't just directly include
>> both libc headers and kernel headers?
>
> including both libc and linux headers is fragile and
> will break differently across the different linux
> libc implementations.
We saw this all the time working in embedded.
There ends up being a rather tight version coupling that
happens, and that's unfortunate, but a function of cost.
Fixing this so it works in the various cases is costly.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-11-07 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALN7hCK0EXLXjPRPr+tuuF2-uQvkLMCFDNzGhv9HS-jrAz6Hmg@mail.gmail.com>
2019-11-07 12:05 ` Continuing the UAPI split Christian Brauner
2019-11-07 12:10 ` Florian Weimer
2019-11-07 13:03 ` Elichai Turkel
2019-11-07 13:23 ` Florian Weimer
2019-11-07 13:36 ` Christian Brauner
2019-11-07 13:47 ` Florian Weimer
2019-11-07 14:05 ` Christian Brauner
2019-11-07 18:02 ` Carlos O'Donell
2019-11-07 16:21 ` Szabolcs Nagy
2019-11-07 18:05 ` Carlos O'Donell [this message]
2019-11-07 20:32 ` Florian Weimer
2019-11-07 22:32 ` Carlos O'Donell
2019-11-08 7:28 ` Florian Weimer
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=086ffddf-553f-453d-a046-4d5e6abead21@redhat.com \
--to=carlos@redhat.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=christian.brauner@ubuntu.com \
--cc=elichai.turkel@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=nd@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.