linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: David Miller <davem@davemloft.net>,
	dwmw2@infradead.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, jarod@redhat.com, jogo@openwrt.org,
	david.heidelberger@ixit.cz, maillist-linux@barfooze.de,
	mikko.rapeli@iki.fi, musl@lists.openwall.com
Subject: Re: [musl] Re: [PATCH v2 0/3] uapi glibc compat: fix musl libc compatibility
Date: Fri, 21 Apr 2017 10:41:51 -0400	[thread overview]
Message-ID: <20170421144151.GF17319@brightrain.aerifal.cx> (raw)
In-Reply-To: <25477d46-b100-ce87-98d9-8c5e02d409b8@hauke-m.de>

On Fri, Apr 21, 2017 at 03:14:21PM +0200, Hauke Mehrtens wrote:
> 
> 
> On 04/20/2017 10:36 PM, David Miller wrote:
> > From: David Woodhouse <dwmw2@infradead.org>
> > Date: Thu, 20 Apr 2017 21:14:37 +0100
> > 
> >> I agree, except I don't think you're going far enough. Those "standard
> >> names" you mention... some of this stuff actually depends on __GLIBC__,
> >> and *that* isn't right either.
> > 
> > Yep, that's something that needs correcting.
> > 
> Should all libc implementations define __GLIBC__

Absolutely not.

Rich

      parent reply	other threads:[~2017-04-21 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 21:00 [PATCH v2 0/3] uapi glibc compat: fix musl libc compatibility Hauke Mehrtens
2017-04-18 21:00 ` [PATCH v2 1/3] uapi glibc compat: add libc compat code when not build for kernel Hauke Mehrtens
2017-04-18 21:00 ` [PATCH v2 2/3] uapi glibc compat: fix build if libc defines IFF_ECHO Hauke Mehrtens
2017-04-18 21:00 ` [PATCH v2 3/3] uapi/if_ether.h: prevent redefinition of struct ethhdr Hauke Mehrtens
2017-04-20 20:07 ` [PATCH v2 0/3] uapi glibc compat: fix musl libc compatibility David Miller
2017-04-20 20:14   ` David Woodhouse
2017-04-20 20:36     ` David Miller
2017-04-21 13:14       ` Hauke Mehrtens
2017-04-21 13:17         ` David Woodhouse
2017-04-21 14:41         ` Rich Felker [this message]

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=20170421144151.GF17319@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=davem@davemloft.net \
    --cc=david.heidelberger@ixit.cz \
    --cc=dwmw2@infradead.org \
    --cc=hauke@hauke-m.de \
    --cc=jarod@redhat.com \
    --cc=jogo@openwrt.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist-linux@barfooze.de \
    --cc=mikko.rapeli@iki.fi \
    --cc=musl@lists.openwall.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).