Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
	 richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] linux-yocto: drop 4.4 recipes
Date: Tue, 28 Feb 2017 13:25:09 -0800	[thread overview]
Message-ID: <1488317109.22952.99.camel@linux.intel.com> (raw)
In-Reply-To: <ebd2ca05bb2fff117f0467bb02762757c469ec6e.1488164498.git.bruce.ashfield@windriver.com>

On Sun, 2017-02-26 at 22:10 -0500, Bruce Ashfield wrote:
> We have 4.1 (LTSI) 4.9 (LTS) and 4.10 as the three kernels in the
> master branch. 4.4 is no longer needed and can be dropped.
> 
Regarding 4.4, this is not exactly true, not everyone has migrated to
the 4.9 LTS as it is still fairly "new" as far as kernel goes, so let's
please preserve 4.4 for one more release.

meta-intel needs to support 4.4 and 4.9 currently.

Sau!

> This kernel will continue to get -stable updates as appropriate, but
> won't get SRCREV updates to the master branch.
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
>  meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   | 36 -----------
> --------
>  meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 23 -------------
>  meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 42 -----------
> ------------
>  3 files changed, 101 deletions(-)
>  delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
>  delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
>  delete mode 100644 meta/recipes-kernel/linux/linux-yocto_4.4.bb
> 
> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
> b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
> deleted file mode 100644
> index 82f1a94f162f..000000000000
> --- a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
> +++ /dev/null
> @@ -1,36 +0,0 @@
> -KBRANCH ?= "standard/preempt-rt/base"
> -
> -require recipes-kernel/linux/linux-yocto.inc
> -
> -# Skip processing of this recipe if it is not explicitly specified
> as the
> -# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when
> trying
> -# to build multiple virtual/kernel providers, e.g. as dependency of
> -# core-image-rt-sdk, core-image-rt.
> -python () {
> -    if d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-
> yocto-rt":
> -        raise bb.parse.SkipPackage("Set
> PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
> -}
> -
> -SRCREV_machine ?= "6622c6471016005d5588aa4338ce57aced713dcd"
> -SRCREV_meta ?= "f4a781388fae67caec79a5a571c8aadef0185044"
> -
> -SRC_URI = "git://git.yoctoproject.org/linux-yocto-
> 4.4.git;branch=${KBRANCH};name=machine \
> -           git://git.yoctoproject.org/yocto-kernel-
> cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
> -
> -LINUX_VERSION ?= "4.4.41"
> -
> -PV = "${LINUX_VERSION}+git${SRCPV}"
> -
> -KMETA = "kernel-meta"
> -KCONF_BSP_AUDIT_LEVEL = "2"
> -
> -LINUX_KERNEL_TYPE = "preempt-rt"
> -
> -COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
> -
> -# Functionality flags
> -KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc
> features/taskstats/taskstats.scc"
> -KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
> -KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
> -KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
> -KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
> b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
> deleted file mode 100644
> index 6cb580dc3e90..000000000000
> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
> +++ /dev/null
> @@ -1,23 +0,0 @@
> -KBRANCH ?= "standard/tiny/common-pc"
> -LINUX_KERNEL_TYPE = "tiny"
> -KCONFIG_MODE = "--allnoconfig"
> -
> -require recipes-kernel/linux/linux-yocto.inc
> -
> -LINUX_VERSION ?= "4.4.41"
> -
> -KMETA = "kernel-meta"
> -KCONF_BSP_AUDIT_LEVEL = "2"
> -
> -SRCREV_machine ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
> -SRCREV_meta ?= "f4a781388fae67caec79a5a571c8aadef0185044"
> -
> -PV = "${LINUX_VERSION}+git${SRCPV}"
> -
> -SRC_URI = "git://git.yoctoproject.org/linux-yocto-
> 4.4.git;branch=${KBRANCH};name=machine \
> -           git://git.yoctoproject.org/yocto-kernel-
> cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
> -
> -COMPATIBLE_MACHINE = "(qemux86$)"
> -
> -# Functionality flags
> -KERNEL_FEATURES = ""
> diff --git a/meta/recipes-kernel/linux/linux-yocto_4.4.bb
> b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
> deleted file mode 100644
> index 34e0f38c030b..000000000000
> --- a/meta/recipes-kernel/linux/linux-yocto_4.4.bb
> +++ /dev/null
> @@ -1,42 +0,0 @@
> -KBRANCH ?= "standard/base"
> -
> -require recipes-kernel/linux/linux-yocto.inc
> -
> -# board specific branches
> -KBRANCH_qemuarm  ?= "standard/arm-versatile-926ejs"
> -KBRANCH_qemuarm64 ?= "standard/qemuarm64"
> -KBRANCH_qemumips ?= "standard/mti-malta32"
> -KBRANCH_qemuppc  ?= "standard/qemuppc"
> -KBRANCH_qemux86  ?= "standard/base"
> -KBRANCH_qemux86-64 ?= "standard/base"
> -KBRANCH_qemumips64 ?= "standard/mti-malta64"
> -
> -SRCREV_machine_qemuarm ?= "60287c1951ca7063bc19597eb5cabf834e660cfb"
> -SRCREV_machine_qemuarm64 ?=
> "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
> -SRCREV_machine_qemumips ?=
> "143d659ae6d53623001e22c13a0286bd6d1723ca"
> -SRCREV_machine_qemuppc ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
> -SRCREV_machine_qemux86 ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
> -SRCREV_machine_qemux86-64 ?=
> "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
> -SRCREV_machine_qemumips64 ?=
> "c74cc42106745bab08de6263b9320ac029f2cca9"
> -SRCREV_machine ?= "ad8b1d659ddd2699ebf7d50ef9de8940b157bfc2"
> -SRCREV_meta ?= "f4a781388fae67caec79a5a571c8aadef0185044"
> -
> -SRC_URI = "git://git.yoctoproject.org/linux-yocto-
> 4.4.git;name=machine;branch=${KBRANCH}; \
> -           git://git.yoctoproject.org/yocto-kernel-
> cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
> -
> -LINUX_VERSION ?= "4.4.41"
> -
> -PV = "${LINUX_VERSION}+git${SRCPV}"
> -
> -KMETA = "kernel-meta"
> -KCONF_BSP_AUDIT_LEVEL = "2"
> -
> -COMPATIBLE_MACHINE =
> "qemuarm|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> -
> -# Functionality flags
> -KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> -KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
> -KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
> -KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
> -KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc
> cfg/paravirt_kvm.scc"
> -KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES",
> "mx32", " cfg/x32.scc", "" ,d)}"
> -- 
> 2.5.0
> 


  reply	other threads:[~2017-02-28 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  3:10 [PATCH 0/4] linux-yocto: kernel version updates Bruce Ashfield
2017-02-27  3:10 ` [PATCH 1/4] linux-yocto: introduce 4.10 recipes Bruce Ashfield
2017-02-27  3:10 ` [PATCH 2/4] libc-headers: introduce 4.10 and set as default Bruce Ashfield
2017-02-27  3:10 ` [PATCH 3/4] linux-yocto-dev: add virtio fragment for virtio targets Bruce Ashfield
2017-02-27  3:10 ` [PATCH 4/4] linux-yocto: drop 4.4 recipes Bruce Ashfield
2017-02-28 21:25   ` Saul Wold [this message]
2017-03-03 14:41 ` [PATCH 0/4] linux-yocto: kernel version updates Burton, Ross
2017-03-03 16:07   ` Burton, Ross

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=1488317109.22952.99.camel@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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