From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel-yocto.bbclass: Fixup shell condition test syntax error
Date: Fri, 26 Sep 2014 15:06:51 -0400 [thread overview]
Message-ID: <5425B94B.5070707@windriver.com> (raw)
In-Reply-To: <6575549ca9a37610b0832055c8cac3c234bd906e.1411758271.git.dvhart@linux.intel.com>
On 14-09-26 03:04 PM, Darren Hart wrote:
> A warning is issued when run about an unexpected operator due to a
> syntax error with an extra if empedded in the shell conditional. Remove
> the extra if.
ouch. How on earth did that survive ?
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
> Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> meta/classes/kernel-yocto.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
> index 929d64a..7718f9a 100644
> --- a/meta/classes/kernel-yocto.bbclass
> +++ b/meta/classes/kernel-yocto.bbclass
> @@ -296,7 +296,7 @@ do_validate_branches() {
> force_srcrev="${SRCREV}"
> else
> git cat-file -t ${machine_srcrev} > /dev/null
> - if [ if $? -ne 0 ]; then
> + if [ $? -ne 0 ]; then
> bberror "${machine_srcrev} is not a valid commit ID."
> bbfatal "The kernel source tree may be out of sync"
> fi
>
prev parent reply other threads:[~2014-09-26 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 19:04 [PATCH] kernel-yocto.bbclass: Fixup shell condition test syntax error Darren Hart
2014-09-26 19:06 ` Bruce Ashfield [this message]
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=5425B94B.5070707@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.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