From: marmeladema <marmeladema@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] kernel-libc-headers: update to 5.15.33
Date: Sat, 09 Apr 2022 22:08:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36606@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
There is a new pull request by marmeladema against master on the void-packages repository
https://github.com/marmeladema/void-packages kernel-libc-headers-5.15
https://github.com/void-linux/void-packages/pull/36606
kernel-libc-headers: update to 5.15.33
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64 (crossbuilds)
A patch file from https://github.com/void-linux/void-packages/pull/36606.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-kernel-libc-headers-5.15-36606.patch --]
[-- Type: text/x-diff, Size: 2026 bytes --]
From 63e93c5a8cc275a276716d7e18bab7f746adf8be Mon Sep 17 00:00:00 2001
From: marmeladema <xademax@gmail.com>
Date: Sat, 9 Apr 2022 22:07:19 +0200
Subject: [PATCH] kernel-libc-headers: update to 5.15.33
---
...-glibc-specific-inclusion-of-sysinfo.h-in-kernel.h.patch | 6 +++---
| 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/kernel-libc-headers/patches/1-4-glibc-specific-inclusion-of-sysinfo.h-in-kernel.h.patch b/srcpkgs/kernel-libc-headers/patches/1-4-glibc-specific-inclusion-of-sysinfo.h-in-kernel.h.patch
index c93e732de0ee..5564ab298a8c 100644
--- a/srcpkgs/kernel-libc-headers/patches/1-4-glibc-specific-inclusion-of-sysinfo.h-in-kernel.h.patch
+++ b/srcpkgs/kernel-libc-headers/patches/1-4-glibc-specific-inclusion-of-sysinfo.h-in-kernel.h.patch
@@ -1,12 +1,12 @@
--- a/include/uapi/linux/kernel.h
+++ b/include/uapi/linux/kernel.h
-@@ -1,7 +1,9 @@
+@@ -2,7 +2,9 @@
#ifndef _UAPI_LINUX_KERNEL_H
#define _UAPI_LINUX_KERNEL_H
+#ifdef __GLIBC__
#include <linux/sysinfo.h>
+#endif
+ #include <linux/const.h>
- /*
- * 'kernel.h' contains some often-used function prototypes etc
+ #endif /* _UAPI_LINUX_KERNEL_H */
--git a/srcpkgs/kernel-libc-headers/template b/srcpkgs/kernel-libc-headers/template
index ff67067469e9..a072a03b0143 100644
--- a/srcpkgs/kernel-libc-headers/template
+++ b/srcpkgs/kernel-libc-headers/template
@@ -1,6 +1,6 @@
# Template file for 'kernel-libc-headers'
pkgname=kernel-libc-headers
-version=5.10.4
+version=5.15.33
revision=1
bootstrap=yes
wrksrc=linux-${version}
@@ -9,7 +9,7 @@ maintainer="Érico Nogueira <ericonr@disroot.org>"
license="GPL-2.0-only"
homepage="http://www.kernel.org"
distfiles="$KERNEL_SITE/kernel/v${version%%.*}.x/linux-${version}.tar.xz"
-checksum=904e396c26e9992a16cd1cc989460171536bed7739bf36049f6eb020ee5d56ec
+checksum=c30a17e6090f9ebf2d8ff58cd6c92c7324b1f4a8b3aa6a7f68850310af05a9c4
if [ "$CHROOT_READY" ]; then
hostmakedepends="perl"
next reply other threads:[~2022-04-09 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 20:08 marmeladema [this message]
2022-06-29 20:42 ` Duncaen
2022-06-30 1:36 ` ahesford
2022-06-30 6:50 ` marmeladema
2022-07-05 14:42 ` ahesford
2022-10-04 2:14 ` github-actions
2022-10-18 2:14 ` [PR PATCH] [Closed]: " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36606@inbox.vuxu.org \
--to=marmeladema@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).