All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Tom Zanussi <tom.zanussi@linux.intel.com>,
	sgw@linux.intel.com,  poky@yoctoproject.org
Subject: Re: [PATCH 1/1] yocto-bsp: Add branch to SRC_URI for custom kernels
Date: Wed, 28 Jan 2015 05:05:24 -0800	[thread overview]
Message-ID: <54C8DE94.8090604@intel.com> (raw)
In-Reply-To: <1cdf161857393965869f0984a6bdf4b2592ca7e4.1422365238.git.tom.zanussi@linux.intel.com>

On 01/27/2015 08:46 AM, Tom Zanussi wrote:
> Without 'branch' in the SRC_URI, a SRCREV specified for a non-master
> KBRANCH will result in a fetch failure since the branch tested by the
> fetcher will default to master, which doesn't contain the SRCREV.
> This fixes the problem by adding branch=KBRANCH to the SRC_URI.
>
> Fixes [Yocto #6518].
>
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> ---
>   .../target/arch/common/recipes-kernel/linux/linux-yocto-custom.bb     | 4 ++--

This does not apply to daisy since daisy uses the older style of file 
naming with the command check.

Sau!


>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.bb b/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.bb
> index 69f598e..80a52e7c 100644
> --- a/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.bb
> +++ b/scripts/lib/bsp/substrate/target/arch/common/recipes-kernel/linux/linux-yocto-custom.bb
> @@ -32,9 +32,9 @@ inherit kernel
>   require recipes-kernel/linux/linux-yocto.inc
>
>   {{ if kernel_choice == "custom" and custom_kernel_remote == "y": }}
> -SRC_URI = "{{=custom_kernel_remote_path}};protocol=git;bareclone=1"
> +SRC_URI = "{{=custom_kernel_remote_path}};protocol=git;bareclone=1;branch=${KBRANCH}"
>   {{ if kernel_choice == "custom" and custom_kernel_remote == "n": }}
> -SRC_URI = "git://{{=custom_kernel_local_path}};protocol=file;bareclone=1"
> +SRC_URI = "git://{{=custom_kernel_local_path}};protocol=file;bareclone=1;branch=${KBRANCH}"
>
>   SRC_URI += "file://defconfig"
>
>



  reply	other threads:[~2015-01-28 13:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 13:39 [PATCH 0/1][daisy] yocto-bsp fix Tom Zanussi
2015-01-27 13:39 ` [PATCH 1/1] yocto-bsp: Add branch to SRC_URI for custom kernels Tom Zanussi
2015-01-28 13:05   ` Saul Wold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-27 13:37 [PATCH 0/1][dizzy] yocto-bsp fix Tom Zanussi
2015-01-27 13:37 ` [PATCH 1/1] yocto-bsp: Add branch to SRC_URI for custom kernels Tom Zanussi

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=54C8DE94.8090604@intel.com \
    --to=saul.wold@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=sgw@linux.intel.com \
    --cc=tom.zanussi@linux.intel.com \
    /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.