From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] runqemu fix for yocto-bsp kernels
Date: Fri, 17 Aug 2012 10:54:39 -0700 [thread overview]
Message-ID: <cover.1345225925.git.scott.a.garman@intel.com> (raw)
The yocto-bsp tool generates kernels with additional strings within
the filename, e.g. zImage-myqemuarm.bin. Loosen the MACHINE detection
regex to work with these filenames.
Fixes [YOCTO #2890].
Scott
The following changes since commit bb74035190c7794fcebaa7f6ba247672a4c34cde:
libsamplerate: depends on libsdnfile (2012-08-17 18:04:12 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib sgarman/runqemu-yocto-bsp-oe
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=runqemu-yocto-bsp
Scott Garman (1):
runqemu: work with yocto-bsp created kernel filenames
scripts/runqemu | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2012-08-17 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 17:54 Scott Garman [this message]
2012-08-17 17:54 ` [PATCH 1/1] runqemu: work with yocto-bsp created kernel filenames Scott Garman
2012-08-20 16:52 ` [PATCH 0/1] runqemu fix for yocto-bsp kernels Saul Wold
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=cover.1345225925.git.scott.a.garman@intel.com \
--to=scott.a.garman@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.