public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/6] linux-yocto: skip kernel meta data branches when finding machine branch
Date: Mon, 26 Oct 2015 11:03:13 -0700	[thread overview]
Message-ID: <1445882593.18706.73.camel@intel.com> (raw)
In-Reply-To: <5ca9afcb13639cc38ed268cae4a82709c148759c.1445631234.git.bruce.ashfield@windriver.com>

On Fri, 2015-10-23 at 16:18 -0400, Bruce Ashfield wrote:
> Before the fetcher validated the specified SRCREV was reachable on a
> specified branch, linux-yocto style kernel's were comparing the value
> of KBRANCH and branch on the SRC_URI and then allowing a SRC_URI
> specified branch to override KBRANCH.
> 
> With the introduction of kernel meta data on the SRC_URI, this routine
> is incorrectly picking up a kernel-cache repository and then attempting
> to apply that branch information to the kernel repository.
> 
> The rationalization of the branch specification is largely no longer
> required, and will may be removed in the future. But for now, to keep
> changes minimal, we can simply not return branch information that comes
> from kernel meta data by checking the 'type' parameter and skipping
> if it is of type 'kmeta'.
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Tested-by: Saul Wold <sgw@linux.intel.com>

> ---
>  meta/classes/kernel-yocto.bbclass | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
> index 325f94c73560..00d9667fe0a6 100644
> --- a/meta/classes/kernel-yocto.bbclass
> +++ b/meta/classes/kernel-yocto.bbclass
> @@ -52,7 +52,9 @@ def get_machine_branch(d, default):
>          parm = urldata.parm
>          if "branch" in parm:
>              branches = urldata.parm.get("branch").split(',')
> -            return branches[0]
> +            btype = urldata.parm.get("type")
> +            if btype != "kmeta":
> +                return branches[0]
>  	    
>      return default
>  




  reply	other threads:[~2015-10-26 18:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 20:18 [PATCH 0/6] linux-yocto: consolidated pull request Bruce Ashfield
2015-10-23 20:18 ` [PATCH 1/6] linux-yocto: axxia configuration updates Bruce Ashfield
2015-10-23 20:18 ` [PATCH 2/6] linux-yocto/4.1: drm/i915: Fix the VBT child device parsing for BSW Bruce Ashfield
2015-10-23 20:18 ` [PATCH 3/6] linux-yocto: nf_tables: Add nf_tables feature Bruce Ashfield
2015-10-23 20:18 ` [PATCH 4/6] kern-tools: avoid duplicate .scc file processing Bruce Ashfield
2015-10-23 20:18 ` [PATCH 5/6] linux-yocto: skip kernel meta data branches when finding machine branch Bruce Ashfield
2015-10-26 18:03   ` Saul Wold [this message]
2015-10-23 20:18 ` [PATCH 6/6] linux-yocto/3.19: fix ARM boot with gcc5.x 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=1445882593.18706.73.camel@intel.com \
    --to=saul.wold@intel.com \
    --cc=bruce.ashfield@windriver.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