From: Stefan Hajnoczi <stefanha@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: trivial-patches@qemu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] trivial: fix comment around qdev_init_nofail()
Date: Wed, 6 Apr 2011 21:42:09 +0100 [thread overview]
Message-ID: <BANLkTi=UAE6264NcV3Yuo57X4Wp-wH2VSQ@mail.gmail.com> (raw)
In-Reply-To: <4D9C6FFF.2060807@msgid.tls.msk.ru>
On Wed, Apr 6, 2011 at 2:51 PM, Michael Tokarev <mjt@tls.msk.ru> wrote:
> Resending (previous attempt was at Wed, 30 Mar 2011).
>
> In previous life qdev_init_nofail() used to call hw_error() which
> did register dump and other scary things. Now it calls
> error_report() and does a regular exit(1). Fix the comment
> to match reality.
>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
> ---
> hw/qdev.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Merged into my trivial-patches tree:
http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/trivial-patches
I will send a pull request so this can be merged into qemu.git.
The trivial patches tree is a new thing that was proposed recently so
here's the background. The idea is to collect small patches that are
easy to review and apply. A single pull request is then sent which a
qemu.git maintainer will apply. This should prevent patches slipping
through the cracks and lingering on the mailing list.
The trivial patches team was announced in yesterdays community call minutes:
http://www.mail-archive.com/kvm@vger.kernel.org/msg51601.html
If you want to know more:
http://wiki.qemu.org/Contribute/TrivialPatches
Stefan
next prev parent reply other threads:[~2011-04-06 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 13:51 [Qemu-devel] [PATCH] trivial: fix comment around qdev_init_nofail() Michael Tokarev
2011-04-06 20:42 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 12:16 Michael Tokarev
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='BANLkTi=UAE6264NcV3Yuo57X4Wp-wH2VSQ@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=trivial-patches@qemu.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).