From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Stephano Cetola <stephano.cetola@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] provide better error message when runqemu-ifup fails
Date: Wed, 31 Aug 2016 00:00:49 +0100 [thread overview]
Message-ID: <1472598049.29583.60.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160829222432.6123-1-stephano.cetola@linux.intel.com>
On Mon, 2016-08-29 at 15:24 -0700, Stephano Cetola wrote:
> If runqemu-ifup fails hen running testimage, a rather cryptic error
> regarding "no tty present" is displayed. If this step fails, we
> should at least point the user at runqemu-gen-tapdevs. A quick search
> of this term in the manual will lead them to "Enabling Runtime Tests
> on QEMU" which should give them all the info they need.
>
> Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com>
> ---
> scripts/runqemu-internal | 1 +
> 1 file changed, 1 insertion(+)
The shortlog needs a prefix, e.g. "scripts/runqemu:" and this patch
will likely need adapting on top of Robert's changes (see master-next).
Cheers,
Richard
prev parent reply other threads:[~2016-08-30 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 22:24 [PATCH] provide better error message when runqemu-ifup fails Stephano Cetola
2016-08-30 23:00 ` 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=1472598049.29583.60.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=stephano.cetola@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox