From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 03/10] mmc-utils: Upgrade to latest git version
Date: Sun, 23 Oct 2016 14:29:50 +0300 [thread overview]
Message-ID: <1477222197-3698-3-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1477222197-3698-1-git-send-email-maxin.john@intel.com>
Upgrade to most recent commit:
2cb6695e8dec00d887bdd5309d1b57d836fcd214
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
meta/recipes-devtools/mmc/mmc-utils_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/mmc/mmc-utils_git.bb b/meta/recipes-devtools/mmc/mmc-utils_git.bb
index 0a8da19..2cba860 100644
--- a/meta/recipes-devtools/mmc/mmc-utils_git.bb
+++ b/meta/recipes-devtools/mmc/mmc-utils_git.bb
@@ -4,7 +4,7 @@ LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://mmc.c;beginline=1;endline=20;md5=fae32792e20f4d27ade1c5a762d16b7d"
SRCBRANCH ?= "master"
-SRCREV = "bb779acfc385d135b32a6998c1d1fceef0491400"
+SRCREV = "2cb6695e8dec00d887bdd5309d1b57d836fcd214"
PV = "0.1"
--
2.4.0
next prev parent reply other threads:[~2016-10-23 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 11:29 [PATCH 01/10] mc: Upgrade 4.8.17 -> 4.8.18 Maxin B. John
2016-10-23 11:29 ` [PATCH 02/10] neon: Upgrade 0.30.1 -> 0.30.2 Maxin B. John
2016-10-23 11:29 ` Maxin B. John [this message]
2016-10-23 11:29 ` [PATCH 04/10] orc: Upgrade 0.4.25 -> 0.4.26 Maxin B. John
2016-10-23 11:29 ` [PATCH 05/10] acpid: Upgrade 2.0.27 -> 2.0.28 Maxin B. John
2016-10-23 11:29 ` [PATCH 06/10] bluez5: Upgrade 5.41 -> 5.42 Maxin B. John
2016-10-23 11:29 ` [PATCH 07/10] harfbuzz: Upgrade 1.3.0 -> 1.3.2 Maxin B. John
2016-10-23 11:29 ` [PATCH 08/10] ethtool: Upgrade 4.6 -> 4.8 Maxin B. John
2016-10-23 11:29 ` [PATCH 09/10] libjpeg-turbo: Upgrade 1.5.0 -> 1.5.1 Maxin B. John
2016-10-23 11:29 ` [PATCH 10/10] libpng: Upgrade 1.6.24 -> 1.6.25 Maxin B. John
2016-10-23 15:59 ` Khem Raj
2016-10-24 7:54 ` Maxin B. John
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=1477222197-3698-3-git-send-email-maxin.john@intel.com \
--to=maxin.john@intel.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