From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] Upgrade qemu to 0.14.0
Date: Wed, 23 Mar 2011 08:17:40 +0800 [thread overview]
Message-ID: <4D893C24.5060002@intel.com> (raw)
In-Reply-To: <1300730833.30423.3993.camel@rex>
Richard Purdie wrote:
>
> On Thu, 2011-03-17 at 11:52 -0700, Khem Raj wrote:
> > This patchset upgrades qemu in oe-core to 0.14.0
> > The script fixes are done to cope for a bug in 0.14.0
> > as well as to get past a console spawning problem for non-nfs image
> > boots
> >
> >
> > Pull URL: git://git.openembedded.org/openembedded-core-contrib
> > Branch: kraj/qemu-update
> > Browse:
> http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/qemu-update
>
> >
> > Thanks,
> > Khem Raj <raj.khem@gmail.com>
> > ---
> >
> >
> > Khem Raj (5):
> > qemu: Upgrade 0.13.0 -> 0.14.0
>
> With this change, I'm just doing some checks that certain things work,
> its still in my pending queue.
>
Khem,
Thanks for your works on qemu upgrade!
Following patches are dropped. 2&3 exist for a pretty long time, I'm not
sure. But any reason to drop ppc-hack.patch?
qemu-ppc-hack.patch
fix-dirent.patch
workaround_bad_futex_headers.patch
For new added patches, it's better to have a simple description
including upstream commit log if have.
larger_default_ram_size.patch: Why pick up 384? 256 or 512 seems to be
more reasonable.
I assume simple tests across all platform(x86/x86-64/arm/ppc/mips) was
done, right:)
> > qemu.inc: Add sh4,sh4eb,mips64,mips64el targets
>
> For this, I'd like to make the list of targets a separate variable. I'm
> happy with your default for OECore, I might take out some of the arches
> for Yocto/Poky.
>
> > lib/oe/patch.py: Cosmetic change to avoid bitbake warning
> > scripts/poky-qemu-internal: Pass -m <mem_size> always on commandline
> > scripts/poky-qemu-internal: Add rw to KERNCMDLINE for non nfs boots
>
> I merged these, thanks.
>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-03-23 0:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 18:52 [PATCH 0/5] Upgrade qemu to 0.14.0 Khem Raj
2011-03-17 18:52 ` [PATCH 1/5] qemu: Upgrade 0.13.0 -> 0.14.0 Khem Raj
2011-03-25 13:33 ` Richard Purdie
2011-03-17 18:52 ` [PATCH 2/5] qemu.inc: Add sh4, sh4eb, mips64, mips64el targets Khem Raj
2011-03-17 18:52 ` [PATCH 3/5] lib/oe/patch.py: Cosmetic change to avoid bitbake warning Khem Raj
2011-03-17 18:52 ` [PATCH 4/5] scripts/poky-qemu-internal: Pass -m <mem_size> always on commandline Khem Raj
2011-03-17 18:52 ` [PATCH 5/5] scripts/poky-qemu-internal: Add rw to KERNCMDLINE for non nfs boots as well Khem Raj
2011-03-21 18:07 ` [PATCH 0/5] Upgrade qemu to 0.14.0 Richard Purdie
2011-03-23 0:17 ` Zhai, Edwin [this message]
2011-03-23 2:06 ` Khem Raj
2011-03-24 0:41 ` Zhai, Edwin
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=4D893C24.5060002@intel.com \
--to=edwin.zhai@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.