From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/clinfo: bump to version 3.0.20.11.20
Date: Thu, 7 Jan 2021 17:09:16 +0100 [thread overview]
Message-ID: <20210107160916.1156610-1-romain.naour@gmail.com> (raw)
Update indentation of hash file (two spaces).
Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
package/clinfo/clinfo.hash | 6 +++---
package/clinfo/clinfo.mk | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/clinfo/clinfo.hash b/package/clinfo/clinfo.hash
index d5766e6322..2528a9e6c8 100644
--- a/package/clinfo/clinfo.hash
+++ b/package/clinfo/clinfo.hash
@@ -1,4 +1,4 @@
# locally calculated
-sha256 64b02e68ccff3b95437bd0bd70dcb88438c58adec16a7145a5d4e5c26a898ccf clinfo-2.2.18.03.26.tar.gz
-sha256 a2010f343487d3f7618affe54f789f5487602331c0a8d03f49e9a7c547cf0499 legalcode.txt
-sha256 2a7a9321be169ea6edbc6b1010e8f7bb0f4c1482a2f65c34a49e9719f129b79a LICENSE
+sha256 3c506083e72e9ee09fc7d5de513be7c5eff0284f198a60fb60ab493f6f0a549a clinfo-3.0.20.11.20.tar.gz
+sha256 a2010f343487d3f7618affe54f789f5487602331c0a8d03f49e9a7c547cf0499 legalcode.txt
+sha256 2a7a9321be169ea6edbc6b1010e8f7bb0f4c1482a2f65c34a49e9719f129b79a LICENSE
diff --git a/package/clinfo/clinfo.mk b/package/clinfo/clinfo.mk
index cf08692316..404e5f7535 100644
--- a/package/clinfo/clinfo.mk
+++ b/package/clinfo/clinfo.mk
@@ -4,7 +4,7 @@
#
################################################################################
-CLINFO_VERSION = 2.2.18.03.26
+CLINFO_VERSION = 3.0.20.11.20
CLINFO_SITE = $(call github,Oblomov,clinfo,$(CLINFO_VERSION))
CLINFO_LICENSE = CC0-1.0
CLINFO_LICENSE_FILES = legalcode.txt LICENSE
--
2.25.4
next reply other threads:[~2021-01-07 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 16:09 Romain Naour [this message]
2021-01-09 22:52 ` [Buildroot] [PATCH] package/clinfo: bump to version 3.0.20.11.20 Yann E. MORIN
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=20210107160916.1156610-1-romain.naour@gmail.com \
--to=romain.naour@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.