Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-antz <the-antz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pinebookpro-kernel: add missing header files
Date: Sun, 25 Oct 2020 19:32:21 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25882@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

There is a new pull request by the-antz against master on the void-packages repository

https://github.com/the-antz/void-packages pbp-dkms
https://github.com/void-linux/void-packages/pull/25882

pinebookpro-kernel: add missing header files
The missing vdso header files prevented dkms from building zfs (and
probably other modules).

They're also included in the upstream 5.8 package https://github.com/void-linux/void-packages/blob/6d11ea5f69d561753a77854017e660a9deb8080d/srcpkgs/linux5.8/template#L182

I successfully cross compiled it on ppc64le (compiles successfully, result untested) and native on aarch64 (compiles successfully, result seems to work fine).
I'm currently building it on aarch64-musl but I'm not sure if that's relevant for a kernel package.

A patch file from https://github.com/void-linux/void-packages/pull/25882.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pbp-dkms-25882.patch --]
[-- Type: text/x-diff, Size: 1284 bytes --]

From cf8da04984bc16d5ff7e4629a852b3884404c320 Mon Sep 17 00:00:00 2001
From: Antz <antzz@protonmail.ch>
Date: Sat, 24 Oct 2020 21:11:44 +0000
Subject: [PATCH] pinebookpro-kernel: add missing header files

The missing vdso header files prevented dkms from building zfs (and
probably other modules).
---
 srcpkgs/pinebookpro-kernel/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/pinebookpro-kernel/template b/srcpkgs/pinebookpro-kernel/template
index 2cfdd54a23b2..97187d41d5e0 100644
--- a/srcpkgs/pinebookpro-kernel/template
+++ b/srcpkgs/pinebookpro-kernel/template
@@ -1,7 +1,7 @@
 # Template file for 'pinebookpro-kernel'
 pkgname=pinebookpro-kernel
 version=5.7.0
-revision=1
+revision=2
 archs="aarch64*"
 _commit=a8f4db8a726e5e4552e61333dcd9ea1ff35f39f9
 wrksrc="linux-pinebook-pro-${_commit}"
@@ -117,7 +117,7 @@ do_install() {
 	# Remove firmware stuff provided by the "linux-firmware" pkg.
 	rm -rf ${DESTDIR}/usr/lib/firmware
 
-	for i in acpi asm-generic clocksource config crypto drm generated linux \
+	for i in acpi asm-generic clocksource config crypto drm generated linux vdso \
 		math-emu media net pcmcia scsi sound trace uapi video xen dt-bindings; do
 		if [ -d include/$i ]; then
 			cp -a include/$i ${hdrdest}/include

             reply	other threads:[~2020-10-25 18:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 18:32 the-antz [this message]
2020-10-25 19:05 ` ericonr
2020-10-25 22:36 ` the-antz
2020-10-26  4:07 ` CameronNemo
2020-10-26 14:50 ` [PR PATCH] [Updated] " the-antz
2020-10-26 14:51 ` the-antz
2020-12-03 21:24 ` the-antz
2020-12-03 21:24 ` [PR PATCH] [Closed]: " the-antz

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-25882@inbox.vuxu.org \
    --to=the-antz@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).