From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/6] linux-yocto-dev: base AUTOREV on specified version
Date: Tue, 6 Jul 2021 02:49:43 +0000 [thread overview]
Message-ID: <f90709882e71f4b21d3e5ab60427769facd0dfba.camel@intel.com> (raw)
In-Reply-To: <CADkTA4Pzsfk+1-D8daFnzmmuqa+7Rj0wDUBY1DDA7uEWzr+x3A@mail.gmail.com>
Hi Bruce,
On Mon, 2021-07-05 at 09:52 -0400, Bruce Ashfield wrote:
> Hi Anuj,
>
> Could you queue this patch for cherry-picking into your next
> hardknott update ?
>
> It is now in master, and I designed it to help folks out using our
> -stable releases so linux-yocto-dev will stay on the version that was
> available in the release timeframe.
Yes, I will include it. Would it also help to switch one of the build
configurations on autobuilder for future releases to use -dev kernel so
it gets built/tested?
Thanks,
Anuj
>
> Bruce
>
> On Wed, Jun 16, 2021 at 4:48 PM <bruce.ashfield@gmail.com> wrote:
> >
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > linux-yocto-dev tracks the latest mainline kernel, and uses
> > standard/* for that support.
> >
> > Archived -dev versions are under v<kernel version>/standard/base.
> >
> > This policy works, except that a released branch will still follow
> > the new kernel versions, causing potential breakage with newer
> > kernels than are supported in that release.
> >
> > Rather than lock the SRCREVs and update branches in old releases,
> > we can preserve the AUTOREV nature of -dev, and allow them to
> > switch automatically to the archived branch based on the
> > LINUX_VERSION
> > in the -dev recipe (which is unchanged in the release branch).
> >
> > This is consistent with the other branch switching done for the
> > kernels and with the -dev workflow.
> >
> > Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> > ---
> > meta/classes/kernel-yocto.bbclass | 24 ++++++++++++++++++++++++
> > 1 file changed, 24 insertions(+)
> >
> > diff --git a/meta/classes/kernel-yocto.bbclass
> > b/meta/classes/kernel-yocto.bbclass
> > index ba139dd7f8..0df61cdef0 100644
> > --- a/meta/classes/kernel-yocto.bbclass
> > +++ b/meta/classes/kernel-yocto.bbclass
> > @@ -631,7 +631,31 @@ do_validate_branches() {
> > # if SRCREV is AUTOREV it shows up as AUTOINC there's
> > nothing to
> > # check and we can exit early
> > if [ "${machine_srcrev}" = "AUTOINC" ]; then
> > +
> > linux_yocto_dev='${@oe.utils.conditional("PREFERRED_PROVIDER_virtua
> > l/kernel", "linux-yocto-dev", "1", "", d)}'
> > + if [ -n "$linux_yocto_dev" ]; then
> > + git checkout -q -f ${machine_branch}
> > + ver=$(grep "^VERSION =" ${S}/Makefile | sed s/.*=\
> > *//)
> > + patchlevel=$(grep "^PATCHLEVEL =" ${S}/Makefile |
> > sed s/.*=\ *//)
> > + sublevel=$(grep "^SUBLEVEL =" ${S}/Makefile | sed
> > s/.*=\ *//)
> > + kver="$ver.$patchlevel"
> > + bbnote "dev kernel: performing version -> branch ->
> > SRCREV validation"
> > + bbnote "dev kernel: recipe version
> > ${LINUX_VERSION}, src version: $kver"
> > + echo "${LINUX_VERSION}" | grep -q $kver
> > + if [ $? -ne 0 ]; then
> > + version="$(echo ${LINUX_VERSION} | sed
> > 's/\+.*$//g')"
> > + versioned_branch="v$version/$machine_branch"
> > +
> > + machine_branch=$versioned_branch
> > + force_srcrev="$(git rev-parse $machine_branch
> > 2> /dev/null)"
> > + if [ $? -ne 0 ]; then
> > + bbfatal "kernel version mismatch detected,
> > and no valid branch $machine_branch detected"
> > + fi
> > +
> > + bbnote "dev kernel: adjusting branch to
> > $machine_branch, srcrev to: $force_srcrev"
> > + fi
> > + else
> > bbnote "SRCREV validation is not required for
> > AUTOREV"
> > + fi
> > elif [ "${machine_srcrev}" = "" ]; then
> > if [ "${SRCREV}" != "AUTOINC" ] && [ "${SRCREV}" !=
> > "INVALID" ]; then
> > # SRCREV_machine_<MACHINE> was not set. This
> > means that a custom recipe
> > --
> > 2.19.1
> >
>
>
next prev parent reply other threads:[~2021-07-06 2:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 20:48 [PATCH 0/6] kernel-yocto: consolidated pull request Bruce Ashfield
2021-06-16 20:48 ` [PATCH 1/6] linux-yocto-dev: base AUTOREV on specified version Bruce Ashfield
2021-07-05 13:52 ` Bruce Ashfield
2021-07-06 2:49 ` Anuj Mittal [this message]
2021-07-06 2:53 ` Bruce Ashfield
2021-07-08 6:29 ` [OE-core] " Anuj Mittal
2021-06-16 20:48 ` [PATCH 2/6] linux-yocto/5.4: update to v5.4.124 Bruce Ashfield
2021-06-16 20:48 ` [PATCH 3/6] linux-yocto/5.10: restore aufs Bruce Ashfield
2021-06-16 20:48 ` [PATCH 4/6] linux-yocto/5.10: update to v5.10.43 Bruce Ashfield
2021-06-16 20:48 ` [PATCH 5/6] linux-yocto/5.4: update to v5.4.125 Bruce Ashfield
2021-06-16 20:48 ` [PATCH 6/6] linux-yocto/5.10: cgroup1: fix leaked context root causing sporadic NULL deref in LTP Bruce Ashfield
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=f90709882e71f4b21d3e5ab60427769facd0dfba.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=bruce.ashfield@gmail.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