From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] iucode-tool: bump to version 2.3.1
Date: Sun, 4 Nov 2018 19:02:40 -0200 [thread overview]
Message-ID: <20181104210241.20237-4-casantos@datacom.com.br> (raw)
In-Reply-To: <20181104210241.20237-1-casantos@datacom.com.br>
Brings several fixes and enhancements. Check the change log at
https://gitlab.com/iucode-tool/iucode-tool/raw/v2.3.1/ChangeLog
Tested on an equipment with Intel C3000 processor.
Signed-off-by: Carlos Santos <casantos@datacom.com.br>
---
package/iucode-tool/iucode-tool.hash | 2 +-
package/iucode-tool/iucode-tool.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/iucode-tool/iucode-tool.hash b/package/iucode-tool/iucode-tool.hash
index 1dab8de978..6d8fb635d0 100644
--- a/package/iucode-tool/iucode-tool.hash
+++ b/package/iucode-tool/iucode-tool.hash
@@ -1,3 +1,3 @@
# Locally computed
-sha256 9810daf925b8a9ca244adc4e1916bcab65601c9ebe87e91c2281f78055982971 iucode-tool_2.2.tar.xz
+sha256 12b88efa4d0d95af08db05a50b3dcb217c0eb2bfc67b483779e33d498ddb2f95 iucode-tool_2.3.1.tar.xz
sha256 ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6 COPYING
diff --git a/package/iucode-tool/iucode-tool.mk b/package/iucode-tool/iucode-tool.mk
index 38f9da438e..e900888d7d 100644
--- a/package/iucode-tool/iucode-tool.mk
+++ b/package/iucode-tool/iucode-tool.mk
@@ -4,7 +4,7 @@
#
################################################################################
-IUCODE_TOOL_VERSION = 2.2
+IUCODE_TOOL_VERSION = 2.3.1
IUCODE_TOOL_SOURCE = iucode-tool_$(IUCODE_TOOL_VERSION).tar.xz
IUCODE_TOOL_SITE = https://gitlab.com/iucode-tool/releases/raw/master
ifeq ($(BR2_PACKAGE_ARGP_STANDALONE),y)
--
2.17.1
next prev parent reply other threads:[~2018-11-04 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 21:02 [Buildroot] [PATCH 0/4] update/improve intel-microcode and iucode-tool Carlos Santos
2018-11-04 21:02 ` [Buildroot] [PATCH 1/4] linux: enable MICROCODE_INTEL if intel-microcode is selected Carlos Santos
2018-11-12 21:37 ` Peter Korsgaard
2018-11-04 21:02 ` [Buildroot] [PATCH 2/4] intel-microcode: bump to version 20180807a Carlos Santos
2018-11-12 21:39 ` Peter Korsgaard
2018-11-04 21:02 ` Carlos Santos [this message]
2018-11-12 21:39 ` [Buildroot] [PATCH 3/4] iucode-tool: bump to version 2.3.1 Peter Korsgaard
2018-11-04 21:02 ` [Buildroot] [PATCH 4/4] iucode-tool: rewrite init script Carlos Santos
2018-11-12 21:47 ` Peter Korsgaard
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=20181104210241.20237-4-casantos@datacom.com.br \
--to=casantos@datacom.com.br \
--cc=buildroot@busybox.net \
/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