From: Adrian Bunk <bunk@stusta.de>
To: Armin Kuster <akuster808@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [warrior-next 06/10] klibc: Fix build with 5.2+ kernel headers
Date: Mon, 30 Sep 2019 11:04:41 +0300 [thread overview]
Message-ID: <20190930080441.GA31191@localhost> (raw)
In-Reply-To: <6748bb66d50cab6acb56a0c4596d9d3c7650e4fb.1569801183.git.akuster808@gmail.com>
This and the other 3 "fix build with 5.2 headers" patches are all for
userspace code that uses the UAPI kernel headers that won't change in
warrior, so these 4 commits are not needed.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-09-30 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 23:54 [warrior-next 00/10] patch review Armin Kuster
2019-09-29 23:54 ` [warrior-next 01/10] tcpdump: Fix CVE-2017-16808 Armin Kuster
2019-09-29 23:55 ` [warrior-next 02/10] redis: Fix build with clang/x86 Armin Kuster
2019-09-29 23:55 ` [warrior-next 03/10] apache2: fix multilib file conflicts Armin Kuster
2019-09-29 23:55 ` [warrior-next 04/10] klibc: Pass -fno-builtin-bcmp with musl/clang combo Armin Kuster
2019-09-29 23:55 ` [warrior-next 05/10] klibc: Disable bcmp builtin for clang on glibc as well Armin Kuster
2019-09-29 23:55 ` [warrior-next 06/10] klibc: Fix build with 5.2+ kernel headers Armin Kuster
2019-09-30 8:04 ` Adrian Bunk [this message]
2019-09-29 23:55 ` [warrior-next 07/10] bpftool.bb: Disable SECURITY_CFLAGS Armin Kuster
2019-09-29 23:55 ` [warrior-next 08/10] linux-atm: Fix build with kernel headers 5.2+ Armin Kuster
2019-09-29 23:55 ` [warrior-next 09/10] can-utils: Fix build with kernel headers >= 5.2 Armin Kuster
2019-09-29 23:55 ` [warrior-next 10/10] dnsmasq: fix build against 5.2 headers Armin Kuster
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=20190930080441.GA31191@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.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