From: Benjamin Esquivel <benjamin.esquivel@linux.intel.com>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] runqemu-internal: Fixes unary operator expected in new TCPSERIAL_PORTNUM
Date: Wed, 26 Aug 2015 16:53:00 -0500 [thread overview]
Message-ID: <1440625980.15187.59.camel@linux.intel.com> (raw)
In-Reply-To: <1440600498-10313-1-git-send-email-anibal.limon@linux.intel.com>
On Wed, 2015-08-26 at 09:48 -0500, Aníbal Limón wrote:
> If $TCPSERIAL_PORTNUM is empty string causes an error because
> expands the expresion to,
>
> $TCPSERIAL_PORTNUM == "" -> == ""
>
> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
> ---
> scripts/runqemu-internal | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
> index b317358..1b1bc9e 100755
> --- a/scripts/runqemu-internal
> +++ b/scripts/runqemu-internal
> @@ -620,7 +620,7 @@ if [ "x$QEMUOPTIONS" = "x" ]; then
> return 1
> fi
>
> -if [ $TCPSERIAL_PORTNUM != "" ]; then
> +if [ "$TCPSERIAL_PORTNUM" != "" ]; then
I believe this would work but if you want to make it bulletproof you'd:
if [ X"$TCPSERIAL_PORTNUM" != X"" ]; then
> if [ "$MACHINE" = "qemuarm64" ]; then
> QEMUOPTIONS="$QEMUOPTIONS -device virtio-serial-device
> -chardev socket,id=virtcon,port=$TCPSERIAL_PORTNUM,host=127.0.0.1
> -device virtconsole,chardev=virtcon"
> else
> --
> 1.9.1
>
next prev parent reply other threads:[~2015-08-26 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 14:48 [PATCH] runqemu-internal: Fixes unary operator expected in new TCPSERIAL_PORTNUM Aníbal Limón
2015-08-26 21:53 ` Benjamin Esquivel [this message]
2015-08-27 16:27 ` Aníbal Limón
2015-08-27 17:08 ` Burton, Ross
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=1440625980.15187.59.camel@linux.intel.com \
--to=benjamin.esquivel@linux.intel.com \
--cc=anibal.limon@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 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.