From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/3] linux-libc-headers: refresh 0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch
Date: Wed, 28 Mar 2018 15:43:06 +0300 [thread overview]
Message-ID: <20180328124308.14893-1-alexander.kanavin@linux.intel.com> (raw)
It's only applied with musl and so was missed in the big batch.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
.../0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch
index a3fa59001d2..064a39193de 100644
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch
@@ -80,12 +80,11 @@ Index: linux-4.15/include/uapi/linux/libc-compat.h
/* Definitions for if.h */
#ifndef __UAPI_DEF_IF_IFCONF
-@@ -262,7 +253,7 @@
+@@ -262,6 +253,6 @@
#define __UAPI_DEF_XATTR 1
#endif
-#endif /* __GLIBC__ */
+#endif /* __KERNEL__ */
- /* Definitions for if_ether.h */
- /* allow libcs like musl to deactivate this, glibc does not implement this. */
+ #endif /* _UAPI_LIBC_COMPAT_H */
--
2.16.1
next reply other threads:[~2018-03-28 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 12:43 Alexander Kanavin [this message]
2018-03-28 12:43 ` [PATCH 2/3] openssl: update 1.0.2n -> 1.0.2o Alexander Kanavin
2018-03-28 12:43 ` [PATCH 3/3] openssl: update 1.1.0g -> 1.1.0h Alexander Kanavin
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=20180328124308.14893-1-alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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