From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pinebookpro-kernel: update to 5.15.43
Date: Fri, 27 May 2022 20:47:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37310@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
There is a new pull request by CameronNemo against master on the void-packages repository
https://github.com/CameronNemo/void-packages pbp-kernel-5.15
https://github.com/void-linux/void-packages/pull/37310
pinebookpro-kernel: update to 5.15.43
[ci skip]
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64 (cross)
A patch file from https://github.com/void-linux/void-packages/pull/37310.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pbp-kernel-5.15-37310.patch --]
[-- Type: text/x-diff, Size: 1171 bytes --]
From 7617ee85940ddf50ed75f9079190008b1ba8fff0 Mon Sep 17 00:00:00 2001
From: Cameron Nemo <cnemo@tutanota.com>
Date: Fri, 27 May 2022 11:45:08 -0700
Subject: [PATCH] pinebookpro-kernel: update to 5.15.43
---
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 8c88917e5a77..e31431b7faa1 100644
--- a/srcpkgs/pinebookpro-kernel/template
+++ b/srcpkgs/pinebookpro-kernel/template
@@ -1,6 +1,6 @@
# Template file for 'pinebookpro-kernel'
pkgname=pinebookpro-kernel
-version=5.15.38
+version=5.15.43
revision=1
archs="aarch64*"
wrksrc="linux-${version%.*}"
@@ -11,7 +11,7 @@ homepage="https://www.kernel.org"
distfiles="https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-${version%.*}.tar.xz
https://cdn.kernel.org/pub/linux/kernel/v5.x/patch-${version}.xz"
checksum="57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8
- b62b570af247d884dd0232f509e4e33c5edf57240b1712733e61c37a1d4b4424"
+ 1bbc662eb57604de70700d6c17fce083b715c40722514554d8c1d6b0f82403c0"
skip_extraction="patch-${version}.xz"
python_version=3
next reply other threads:[~2022-05-27 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 18:47 CameronNemo [this message]
2022-05-30 17:06 ` [PR PATCH] [Updated] " CameronNemo
2022-05-30 17:07 ` CameronNemo
2022-06-11 6:50 ` [PR PATCH] [Updated] pinebookpro-kernel: update to 5.15.44 CameronNemo
2022-06-14 16:00 ` pinebookpro-kernel: fix musl, update to 5.15.46 sgn
2022-06-14 16:00 ` [PR PATCH] [Merged]: " sgn
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-37310@inbox.vuxu.org \
--to=cameronnemo@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).