[meta-intel] [PATCH] linux-intel/4.14: update SRCREV to 4.14.66

[Anuj Mittal]

Merge to stable branches would take a bit more time because of extra
testing required which is currently in progress.

Thanks,
Anuj

On 08/24/2018 06:49 PM, Kravchuk, Oleksandr wrote:
> Anuj -
> 
> Apply it to other branches (e.g. rocko and sumo), please. Thanks.
> 
> --
> Yes, this is my signature
> ________________________________________
> From: meta-intel-bounces at yoctoproject.org [meta-intel-bounces at yoctoproject.org] on behalf of Anuj Mittal [anuj.mittal at intel.com]
> Sent: Friday, August 24, 2018 9:01
> To: meta-intel at yoctoproject.org
> Subject: [meta-intel] [PATCH] linux-intel/4.14: update SRCREV to 4.14.66
> 
> Signed-off-by: Anuj Mittal <anuj.mittal at intel.com>
> ---
>  recipes-kernel/linux/linux-intel_4.14.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-intel_4.14.bb b/recipes-kernel/linux/linux-intel_4.14.bb
> index f2d5551..5d6dc7e 100644
> --- a/recipes-kernel/linux/linux-intel_4.14.bb
> +++ b/recipes-kernel/linux/linux-intel_4.14.bb
> @@ -8,8 +8,8 @@ SRC_URI_append = " file://0001-perf-x86-32-explicitly-include-errno.h.patch"
> 
>  DEPENDS += "elfutils-native openssl-native util-linux-native"
> 
> -LINUX_VERSION ?= "4.14.59"
> -SRCREV_machine ?= "a36b9969b6b2c9321d9c6e907b47211be0f4b99c"
> +LINUX_VERSION ?= "4.14.66"
> +SRCREV_machine ?= "dd6a8b48d41ebf5e751b28fb6b7bc0e39f98418b"
>  SRCREV_meta ?= "8a3be7d783a39b56796e1d5197cb9f757e38f22f"
> 
>  # For Crystalforest and Romley
> --
> 2.17.1
> 
> --
> _______________________________________________
> meta-intel mailing list
> meta-intel at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel
> 
> ________________________________
> 
> This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you.
>