From: Randy MacLeod <Randy.MacLeod@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] i2c-tools: uprev to 3.1.2
Date: Wed, 8 Jul 2015 19:36:28 -0400 [thread overview]
Message-ID: <1436398588-18230-1-git-send-email-Randy.MacLeod@windriver.com> (raw)
The only changes based on the CHANGES file are:
decode-dimms: Fix DDR3 extended temp range refresh rate decoding
py-smbus: Add support for python 3
The python3 changes use python3 as the default and 2 as the fallback.
py-smbus is not currently built so no python changes have been made.
The local copy of Module.mk is unchanged aside from moving it to
a directory that is not version specific to avoid uprev noise.
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
---
meta/recipes-devtools/i2c-tools/{i2c-tools-3.1.1 => files}/Module.mk | 0
.../i2c-tools/{i2c-tools_3.1.1.bb => i2c-tools_3.1.2.bb} | 4 ++--
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/i2c-tools/{i2c-tools-3.1.1 => files}/Module.mk (100%)
rename meta/recipes-devtools/i2c-tools/{i2c-tools_3.1.1.bb => i2c-tools_3.1.2.bb} (87%)
diff --git a/meta/recipes-devtools/i2c-tools/i2c-tools-3.1.1/Module.mk b/meta/recipes-devtools/i2c-tools/files/Module.mk
similarity index 100%
rename from meta/recipes-devtools/i2c-tools/i2c-tools-3.1.1/Module.mk
rename to meta/recipes-devtools/i2c-tools/files/Module.mk
diff --git a/meta/recipes-devtools/i2c-tools/i2c-tools_3.1.1.bb b/meta/recipes-devtools/i2c-tools/i2c-tools_3.1.2.bb
similarity index 87%
rename from meta/recipes-devtools/i2c-tools/i2c-tools_3.1.1.bb
rename to meta/recipes-devtools/i2c-tools/i2c-tools_3.1.2.bb
index 71c98a4..92f4d69 100644
--- a/meta/recipes-devtools/i2c-tools/i2c-tools_3.1.1.bb
+++ b/meta/recipes-devtools/i2c-tools/i2c-tools_3.1.2.bb
@@ -6,8 +6,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
SRC_URI = "http://dl.lm-sensors.org/i2c-tools/releases/${BP}.tar.bz2 \
file://Module.mk \
"
-SRC_URI[md5sum] = "0fdbff53ebd0b8d9249256d6c56480b1"
-SRC_URI[sha256sum] = "14d4d7d60d1c12e43f2befe239c682a5c44c27682f153d4b58c1e392d2db1700"
+SRC_URI[md5sum] = "7104a1043d11a5e2c7b131614eb1b962"
+SRC_URI[sha256sum] = "db5e69f2e2a6e3aa2ecdfe6a5f490b149c504468770f58921c8c5b8a7860a441"
inherit autotools-brokensep
--
1.9.1
reply other threads:[~2015-07-08 23:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1436398588-18230-1-git-send-email-Randy.MacLeod@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.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