All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: meta-freescale <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-ppc] [PATCH] classes/u-boot: Update getVar syntax
Date: Wed, 17 Feb 2016 08:31:34 +0000	[thread overview]
Message-ID: <1455697894.28376.37.camel@linuxfoundation.org> (raw)
In-Reply-To: <1454763643.27087.303.camel@linuxfoundation.org>

On Sat, 2016-02-06 at 13:00 +0000, Richard Purdie wrote:
> This runs:
> 
> sed -e 's:\(\.getVar([^,()]*\)):\1, False):g' -i `grep -ril getVar *`
> 
> on the layer to update the getVar usages without an expand parameter,
> This ensures the layer continues to work with bitbake master.
> 
> There is no functionality change although some of these sites
> may benefit from expand=True.
> 
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>  classes/qoriq_build_64bit_kernel.bbclass   | 14 +++++++-------
>  recipes-bsp/u-boot/u-boot-qoriq_2015.01.bb |  6 +++---
>  2 files changed, 10 insertions(+), 10 deletions(-)

Could someone *please* merge this patch to meta-fsl-ppc. If this isn't
merged, we can't move forward with the variable transition since the
autobuilder includes this layer in its automated tests. I appreciate
there have been holidays but this does need to get dealt with.

I'd also note that openssl is failing to build in meta-fsl-ppc after
the no-static libs change to poky.

Cheers,

Richard


  reply	other threads:[~2016-02-17  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 13:00 [meta-fsl-ppc] [PATCH] classes/u-boot: Update getVar syntax Richard Purdie
2016-02-17  8:31 ` Richard Purdie [this message]
2016-02-18  5:00   ` Ting Liu
2016-02-18 16:43     ` Richard Purdie

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=1455697894.28376.37.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=meta-freescale@yoctoproject.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 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.