Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] qemu-script: Fix qemu segfault with Nvidia's proprietary driver
Date: Mon, 09 May 2011 15:56:53 +0800	[thread overview]
Message-ID: <4DC79E45.3020601@intel.com> (raw)
In-Reply-To: <4DC49C10.4060507@linux.intel.com>



Saul Wold wrote:
>
> On 05/06/2011 01:36 AM, Zhai Edwin wrote:
> >
> >
> > Pull URL: git://git.pokylinux.org/poky-contrib.git
> >    Branch: gzhai/fix3
> >    Browse: 
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=gzhai/fix3
> >
> > Zhai Edwin (1):
> >    qemu-script: Fix qemu seg fault if install Nvidia proprietary 
> driver.
> >
> >   scripts/poky-qemu-internal |   13 +++++++++++--
>
> I think that you are using the old script name, I think that you should
> be changing runqemu-internal, not poky-qemu-internal
>

Done. Pls. pull @ the same branch
Thanks,
edwin

> Please correct this.
>
> Sau!
>
> >   1 files changed, 11 insertions(+), 2 deletions(-)
> >
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2011-05-09  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  8:36 [PATCH 0/1] qemu-script: Fix qemu segfault with Nvidia's proprietary driver Zhai Edwin
2011-05-06  8:36 ` [PATCH 1/1] qemu-script: Fix qemu seg fault if install Nvidia " Zhai Edwin
2011-05-07  1:10 ` [PATCH 0/1] qemu-script: Fix qemu segfault with Nvidia's " Saul Wold
2011-05-09  7:56   ` Zhai, Edwin [this message]
2011-05-10 15:25 ` 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=4DC79E45.3020601@intel.com \
    --to=edwin.zhai@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@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