All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Add extra parameters for qemu script
Date: Sun, 12 Dec 2010 18:16:28 -0800	[thread overview]
Message-ID: <4D0581FC.2030600@intel.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D3065973312DC52B@shsmsx501.ccr.corp.intel.com>

On 12/12/2010 05:43 PM, Ke, Liping wrote:
>> I tend to feel that this approach is more flexible, and scales better
>>> than having to support each and every qemu option with our own script
>>> syntax. Is this acceptable, or should we continue to support our own
>>> custom options in addition to Criping's new approach?
>>
>> My gut feeling is that having some simplified way to trigger possibly
>> complex option combinations is still desirable but adding a way to pass
>> additional custom commandline is equally good. This gives us the
>> maximum
>> flexibility moving forwards but keeps the script easy to use?
>>
>
> Hi, Scott
>
> So the conclusion is that I should keep the old (serial nographic) option while
> adding the new "<-XXX -XXX -XXX>" option?
> OK. I will send out the modified patch to you for review later.

Yes, please respin the patch with those changes.

Thanks!

Scott

-- 
Scott Garman
Embedded Linux Distro Engineer - Yocto Project


  reply	other threads:[~2010-12-13  2:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  8:44 Add extra parameters for qemu script Ke, Liping
2010-12-09 20:44 ` Scott Garman
2010-12-09 21:16   ` Zhang, Jessica
2010-12-10 13:34   ` Richard Purdie
2010-12-13  1:43     ` Ke, Liping
2010-12-13  2:16       ` Scott Garman [this message]
2010-12-14  3:41         ` Ke, Liping
2010-12-14 22:27           ` Scott Garman
2010-12-14 22:29             ` Scott Garman
2010-12-15  1:17               ` Ke, Liping

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=4D0581FC.2030600@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=liping.ke@intel.com \
    --cc=yocto@yoctoproject.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.