From: Anuj Mittal <anuj.mittal@intel.com>
To: yocto@yoctoproject.org
Subject: [meta-yocto][PATCH v2 3/3] linux-yocto: update genericx86* SRCREVs for 4.15
Date: Wed, 28 Mar 2018 14:19:39 +0800 [thread overview]
Message-ID: <1522217979-669-4-git-send-email-anuj.mittal@intel.com> (raw)
In-Reply-To: <1522217979-669-1-git-send-email-anuj.mittal@intel.com>
Bump to stable kernel release 4.15.13.
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.15.bbappend | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.15.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.15.bbappend
index a30a924..9ae1735 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.15.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.15.bbappend
@@ -4,11 +4,11 @@ KBRANCH_genericx86-64 = "v4.15/standard/base"
KMACHINE_genericx86 ?= "common-pc"
KMACHINE_genericx86-64 ?= "common-pc-64"
-SRCREV_machine_genericx86 ?= "a6a3a6a73d628798fc6eb6832bf829a9ea43f6bd"
-SRCREV_machine_genericx86-64 ?= "a6a3a6a73d628798fc6eb6832bf829a9ea43f6bd"
+SRCREV_machine_genericx86 ?= "f73fd8783a3e7529902366ba75aafb81c19ec3c9"
+SRCREV_machine_genericx86-64 ?= "f73fd8783a3e7529902366ba75aafb81c19ec3c9"
COMPATIBLE_MACHINE_genericx86 = "genericx86"
COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
-LINUX_VERSION_genericx86 = "4.15.3"
-LINUX_VERSION_genericx86-64 = "4.15.3"
+LINUX_VERSION_genericx86 = "4.15.13"
+LINUX_VERSION_genericx86-64 = "4.15.13"
--
2.7.4
prev parent reply other threads:[~2018-03-28 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 6:19 [meta-yocto][PATCH v2 0/3] Update SRCREVs for genericx86* BSPs Anuj Mittal
2018-03-28 6:19 ` [meta-yocto][PATCH v2 1/3] linux-yocto: update genericx86* SRCREVs for 4.12 Anuj Mittal
2018-03-28 6:19 ` [meta-yocto][PATCH v2 2/3] linux-yocto: update genericx86* SRCREVs for 4.14 Anuj Mittal
2018-03-28 6:19 ` Anuj Mittal [this message]
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=1522217979-669-4-git-send-email-anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--cc=yocto@yoctoproject.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 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.