All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: 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: Fri, 06 May 2011 18:10:40 -0700	[thread overview]
Message-ID: <4DC49C10.4060507@linux.intel.com> (raw)
In-Reply-To: <cover.1304670670.git.edwin.zhai@intel.com>

On 05/06/2011 01:36 AM, Zhai Edwin wrote:
> From: Zhai Edwin<edwin.zhai@intel.com>
>
> Previsous solution is only giving warnings as different distro has different
> path of mesa libGL. This patch try to use different path for different distro
> after looking at /etc/lsb-release per Raj's suggestion. Ubuntu is there, and
> other distro handling can be easily added.
>
> 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
>
> Thanks,
>      Zhai Edwin<edwin.zhai@intel.com>
> ---
>
>
> 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

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



  parent reply	other threads:[~2011-05-07  1:13 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 ` Saul Wold [this message]
2011-05-09  7:56   ` [PATCH 0/1] qemu-script: Fix qemu segfault with Nvidia's " Zhai, Edwin
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=4DC49C10.4060507@linux.intel.com \
    --to=sgw@linux.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.