From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: jordan.l.justen@intel.com, qemu-devel@nongnu.org,
anthony@codemonkey.ws, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] pc_sysfw: Check for qemu_find_file() failure
Date: Thu, 16 Aug 2012 15:58:47 +0200 [thread overview]
Message-ID: <502CFC97.7010602@redhat.com> (raw)
In-Reply-To: <87txw3djyc.fsf@blackfin.pond.sub.org>
Am 16.08.2012 15:50, schrieb Markus Armbruster:
>> Although I'm not sure it qualifies for hard-freeze...
>
> I didn't tag my series "for-1.2". I understand that fixes to
> not-so-important stuff aren't welcome at this time even when they're
> really simple.
It's a clear bug fix, easy to understand and low risk, and even rc0
isn't out yet. I think this would still be fine for 1.2.
Kevin
next prev parent reply other threads:[~2012-08-16 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 11:41 [Qemu-devel] [PATCH 0/2] Fix two buggy pc_sysfw error paths Markus Armbruster
2012-08-16 11:41 ` [Qemu-devel] [PATCH 1/2] pc_sysfw: Check for qemu_find_file() failure Markus Armbruster
2012-08-16 13:30 ` Luiz Capitulino
2012-08-16 13:50 ` Markus Armbruster
2012-08-16 13:58 ` Kevin Wolf [this message]
2012-08-16 14:03 ` Luiz Capitulino
2012-08-16 14:32 ` Markus Armbruster
2012-08-16 14:49 ` Luiz Capitulino
2012-08-16 15:12 ` Markus Armbruster
2012-08-16 16:49 ` Luiz Capitulino
2012-08-16 17:58 ` Luiz Capitulino
2012-08-16 17:10 ` Jordan Justen
2012-08-16 11:41 ` [Qemu-devel] [PATCH 2/2] pc_sysfw: Plug memory leak on pc_fw_add_pflash_drv() error path Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2012-11-23 18:12 [Qemu-trivial] [PATCH 0/2] pc_fw_add_pflash_drv() fixes Markus Armbruster
2012-11-23 18:12 ` [Qemu-devel] [PATCH 1/2] pc_sysfw: Check for qemu_find_file() failure Markus Armbruster
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=502CFC97.7010602@redhat.com \
--to=kwolf@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=jordan.l.justen@intel.com \
--cc=lcapitulino@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 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.