From: Hauke Mehrtens <hauke@hauke-m.de>
To: davem@davemloft.net
Cc: 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
Subject: Re: [PATCH 0/4] uapi glibc compat: fix musl libc compatibility
Date: Tue, 28 Mar 2017 14:01:33 +0200 [thread overview]
Message-ID: <0ec2bb3196283b5268da1e2e27962a1b@hauke-m.de> (raw)
In-Reply-To: <20170312220039.16885-1-hauke@hauke-m.de>
On 2017-03-12 23:00, Hauke Mehrtens wrote:
> The code from libc-compat.h depends on some glibc specific defines and
> causes compile problems with the musl libc. These patches remove some
> of the glibc dependencies. With these patches the LEDE (OpenWrt) base
> user space applications can be build with unmodified kernel headers and
> musl libc.
>
> This was compile tested with the user space from LEDE (OpenWrt) with
> musl 1.1.16, glibc 2.25 and uClibc-ng 1.0.22.
>
> David Heidelberger (1):
> uapi/if_ether.h: prevent redefinition of struct ethhdr
>
> Hauke Mehrtens (3):
> uapi glibc compat: add libc compat code when not build for kernel
> uapi glibc compat: fix build if libc defines IFF_ECHO
> uapi glibc compat: Do not check for __USE_MISC
>
> include/uapi/linux/if_ether.h | 3 +++
> include/uapi/linux/libc-compat.h | 25 +++++++++++++++++++------
> 2 files changed, 22 insertions(+), 6 deletions(-)
Did I send this to the correct maintainer? I am unsure through which
maintainer this should go. I saw that some patches for the libc-compat.h
file went trough David Miller, so I tried the same.
Hauke
prev parent reply other threads:[~2017-03-28 12:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 22:00 Hauke Mehrtens
2017-03-12 22:00 ` [PATCH 1/4] uapi glibc compat: add libc compat code when not build for kernel Hauke Mehrtens
2017-03-13 11:28 ` Mikko Rapeli
2017-03-12 22:00 ` [PATCH 2/4] uapi glibc compat: fix build if libc defines IFF_ECHO Hauke Mehrtens
2017-03-13 11:28 ` Mikko Rapeli
2017-03-12 22:00 ` [PATCH 3/4] uapi glibc compat: Do not check for __USE_MISC Hauke Mehrtens
2017-03-13 11:29 ` Mikko Rapeli
2017-03-16 7:59 ` David Woodhouse
2017-03-16 8:26 ` Mikko Rapeli
2017-03-17 18:17 ` Hauke Mehrtens
2017-03-12 22:00 ` [PATCH 4/4] uapi/if_ether.h: prevent redefinition of struct ethhdr Hauke Mehrtens
2017-03-13 11:31 ` Mikko Rapeli
2017-03-28 12:01 ` Hauke Mehrtens [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=0ec2bb3196283b5268da1e2e27962a1b@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=davem@davemloft.net \
--cc=david.heidelberger@ixit.cz \
--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=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
all inboxes | Powered by JetHome®