From: tuxliban <tuxliban@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] intel-ucode: update to 20220419
Date: Thu, 21 Apr 2022 06:49:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36793@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
There is a new pull request by tuxliban against master on the void-packages repository
https://github.com/tuxliban/void-packages intel-ucode
https://github.com/void-linux/void-packages/pull/36793
intel-ucode: update to 20220419
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/36793.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-intel-ucode-36793.patch --]
[-- Type: text/x-diff, Size: 1125 bytes --]
From c631a38d0bcaed6870f1a6f5a4cad44396f8429c Mon Sep 17 00:00:00 2001
From: Tuxliban Torvalds <tenshalito@gmail.com>
Date: Wed, 20 Apr 2022 23:41:51 -0500
Subject: [PATCH] intel-ucode: update to 20220419
---
srcpkgs/intel-ucode/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/intel-ucode/template b/srcpkgs/intel-ucode/template
index 642dee9f7c27..e7e57d0f6588 100644
--- a/srcpkgs/intel-ucode/template
+++ b/srcpkgs/intel-ucode/template
@@ -1,6 +1,6 @@
# Template file for 'intel-ucode'
pkgname=intel-ucode
-version=20220207
+version=20220419
revision=1
archs="i686* x86_64*"
wrksrc="Intel-Linux-Processor-Microcode-Data-Files-microcode-${version}"
@@ -9,7 +9,7 @@ maintainer="Andrew J. Hesford <ajh@sideband.org>"
license="custom: Proprietary"
homepage="https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files"
distfiles="${homepage}/archive/microcode-${version}.tar.gz"
-checksum=532527bd17f3ea6664452b536699818a3bf896e4ace689a43a73624711b7c921
+checksum=b8838d300e749c1dd55d8865bdd49dee5153beb5e29d4b0e613aee475e0c0881
repository=nonfree
do_install() {
next reply other threads:[~2022-04-21 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 4:49 tuxliban [this message]
2022-04-24 13:47 ` [PR PATCH] [Merged]: " ahesford
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-36793@inbox.vuxu.org \
--to=tuxliban@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).