qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: john cooper <john.cooper@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/7] cpu model bug fixes and definition corrections
Date: Tue, 24 May 2011 14:19:00 +0200	[thread overview]
Message-ID: <4DDBA234.1050708@siemens.com> (raw)
In-Reply-To: <4DDAD5D9.8030406@redhat.com>

Starting with this patch, the series lacks proper subjects. Please also
avoid such long subject lines. The background can be explained in the
introduction mail (threading your mails would be nice as well, check git
format-patch). Rather us short tags for the patches, describing the
subsystem/target-arch they touch.

On 2011-05-23 23:47, john cooper wrote:
> Failure by qemu to open a default config file isn't cause to
> error exit -- it just quietly continues on.   After puzzling
> issues with otherwise opaque config file locations and
> startup handling numerous times, some help from qemu seemed
> justified.
> 
> In the case of a "?" pseudo filename arg to -readconfig,
> verbose open of all config files will be enabled.  Normal
> handling of config files is otherwise unaffected by this
> option.
> 
> Note: other CLI flag schemes have been discussed at length
> to accommodate this option.  However given the constraints
> of the existing user interface, a solution which minimally
> impacts the user is ultimately required.

Does this patch also fix the loading of CPU configs when starting qemu
directly from the build folder? That would be warmly welcome!

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

      reply	other threads:[~2011-05-24 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 21:47 [Qemu-devel] [PATCH 4/7] cpu model bug fixes and definition corrections john cooper
2011-05-24 12:19 ` Jan Kiszka [this message]

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=4DDBA234.1050708@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aliguori@us.ibm.com \
    --cc=john.cooper@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).