From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] linux: update to 5.18.
Date: Tue, 05 Jul 2022 22:19:22 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37878@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
There is a new pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages update/linux
https://github.com/void-linux/void-packages/pull/37878
linux: update to 5.18.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
zfs support is done, any blockers from nvidia @abenson ?
A patch file from https://github.com/void-linux/void-packages/pull/37878.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/linux-37878.patch --]
[-- Type: text/x-diff, Size: 591 bytes --]
From 65f9244059d1ed908bdd7ea04b9756233e178091 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Tue, 5 Jul 2022 16:18:22 -0400
Subject: [PATCH] linux: update to 5.18.
---
srcpkgs/linux/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/linux/template b/srcpkgs/linux/template
index f76a6a1d27e8..965a96997a33 100644
--- a/srcpkgs/linux/template
+++ b/srcpkgs/linux/template
@@ -1,6 +1,6 @@
# Template file for 'linux'
pkgname=linux
-version=5.15
+version=5.18
revision=1
build_style=meta
depends="linux${version} linux-base"
next reply other threads:[~2022-07-05 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 20:19 classabbyamp [this message]
2022-07-05 20:42 ` abenson
2022-07-05 21:45 ` abenson
2022-07-07 15:13 ` [PR PATCH] [Merged]: " leahneukirchen
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-37878@inbox.vuxu.org \
--to=classabbyamp@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).