All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	musl@lists.openwall.com, David Woodhouse <dwmw2@infradead.org>,
	Felix Janda <felix.janda@posteo.de>,
	linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>, linux-api@vger.kernel.org
Subject: Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
Date: Fri, 2 Jun 2017 09:07:26 +0200	[thread overview]
Message-ID: <74e5c515-d924-c4d8-69ad-aeb57d1c4ef0@redhat.com> (raw)
In-Reply-To: <9f591383-6e4c-c231-1e5b-68e4b8c16d94@redhat.com>

On 04/25/2017 02:29 PM, Carlos O'Donell wrote:
> In glibc right now we support including linux or glibc header files first,
> and this has always been a requirement from the start. This requirement dictates
> that the kernel know which libc it's being used with so it can tailor coordination.

“right now we support” is not a support commitment, but more of an
aspiration, right?

A lot of combinations are broken, especially when kernel headers are
included first.  Maybe it's time for us to admit defeat and come up with
a simpler scheme which actually works.

Thanks,
Florian

WARNING: multiple messages have this Message-ID (diff)
From: Florian Weimer <fweimer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Carlos O'Donell <carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>,
	musl-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org,
	David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Felix Janda <felix.janda-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: "David S. Miller" <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [musl] Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions
Date: Fri, 2 Jun 2017 09:07:26 +0200	[thread overview]
Message-ID: <74e5c515-d924-c4d8-69ad-aeb57d1c4ef0@redhat.com> (raw)
In-Reply-To: <9f591383-6e4c-c231-1e5b-68e4b8c16d94-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 04/25/2017 02:29 PM, Carlos O'Donell wrote:
> In glibc right now we support including linux or glibc header files first,
> and this has always been a requirement from the start. This requirement dictates
> that the kernel know which libc it's being used with so it can tailor coordination.

“right now we support” is not a support commitment, but more of an
aspiration, right?

A lot of combinations are broken, especially when kernel headers are
included first.  Maybe it's time for us to admit defeat and come up with
a simpler scheme which actually works.

Thanks,
Florian

  parent reply	other threads:[~2017-06-02  7:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 12:08 [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions Felix Janda
2017-03-08 12:46 ` David Woodhouse
2017-03-08 16:39   ` Carlos O'Donell
2017-04-25  6:45     ` [musl] " Hauke Mehrtens
2017-04-25  6:45       ` Hauke Mehrtens
2017-04-25 12:29       ` Carlos O'Donell
2017-04-25 12:29         ` Carlos O'Donell
2017-04-25 17:00         ` [musl] " Rich Felker
2017-04-25 17:00           ` Rich Felker
2017-06-02  7:07         ` Florian Weimer [this message]
2017-06-02  7:07           ` [musl] " Florian Weimer
2017-04-25  6:37   ` Hauke Mehrtens
2017-04-25  6:37     ` Hauke Mehrtens
2017-04-25 12:13     ` Carlos O'Donell
2017-04-25 12:13       ` Carlos O'Donell
2017-07-08 20:27       ` Felix Janda
2017-07-08 20:27         ` Felix Janda
2017-03-08 15:53 ` Carlos O'Donell
2017-03-08 16:25   ` [musl] " Rich Felker
2017-03-08 16:25     ` Rich Felker
2017-03-08 17:29     ` [musl] " Carlos O'Donell
2017-03-08 17:29       ` Carlos O'Donell
2017-03-09  0:14   ` Szabolcs Nagy
2017-03-09  0:51     ` Carlos O'Donell
2017-03-09  2:01       ` [musl] " Rich Felker
2017-03-09  2:01         ` Rich Felker
2017-04-25 13:22     ` Florian Weimer
2017-04-25 13:22       ` 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=74e5c515-d924-c4d8-69ad-aeb57d1c4ef0@redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=felix.janda@posteo.de \
    --cc=hauke@hauke-m.de \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=musl@lists.openwall.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.