From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Scott Garman <scott.a.garman@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] runqemu: work with tap device names that end with a colon
Date: Mon, 24 Sep 2012 11:25:04 +0100 [thread overview]
Message-ID: <1348482304.4654.15.camel@ted> (raw)
In-Reply-To: <788ce6395c57aae824d913c5c9073801a9732c69.1348265025.git.scott.a.garman@intel.com>
On Fri, 2012-09-21 at 15:06 -0700, Scott Garman wrote:
> On Fedora systems (and likely others), ifconfig returns interface
> names that end with a colon. Make sure we strip the colon off the
> tap device name before using it.
>
> This fixes [YOCTO #3028]
>
> Signed-off-by: Scott Garman <scott.a.garman@intel.com>
> ---
> scripts/runqemu-gen-tapdevs | 2 +-
> scripts/runqemu-internal | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-09-24 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 22:06 [PATCH 0/1] runqemu tap device fix Scott Garman
2012-09-21 22:06 ` [PATCH 1/1] runqemu: work with tap device names that end with a colon Scott Garman
2012-09-24 10:25 ` Richard Purdie [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=1348482304.4654.15.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox