From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Hu Tao <hutao@cn.fujitsu.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] pvpanic: initialization cleanup
Date: Wed, 19 Jun 2013 17:13:03 +0300 [thread overview]
Message-ID: <20130619141303.GA5927@redhat.com> (raw)
In-Reply-To: <51C1BB1F.3000305@redhat.com>
On Wed, Jun 19, 2013 at 04:07:27PM +0200, Laszlo Ersek wrote:
> On 06/18/13 15:01, Michael S. Tsirkin wrote:
> > Avoid use of static variables: PC systems
> > initialize pvpanic device through pvpanic_init,
> > so we can simply create the fw_cfg file at that point.
> > This also makes it possible to assert if fw_cfg is not there
> > rather than skipping the device silently.
> >
> > Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> >
> > Changes from v1:
> > don't assert if !fw_cfg, simply skip fwcfg
> >
> > hw/misc/pvpanic.c | 26 ++++++++++++++------------
> > 1 file changed, 14 insertions(+), 12 deletions(-)
>
> Patches look good, however I think you missed to update the 1/2 commit
> message completely. You removed the sentence
>
> Others don't use fw_cfg at all.
>
> but
>
> This also makes it possible to assert if fw_cfg is not there rather
> than skipping the device silently.
>
> remains, although it's exactly the assert() that's been erased.
>
> Laszlo
Good point. It's going in through my tree so I'll tweak the
commit log but won't repost.
Thanks a lot for the thorough review!
prev parent reply other threads:[~2013-06-19 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 13:01 [Qemu-devel] [PATCH v2 1/2] pvpanic: initialization cleanup Michael S. Tsirkin
2013-06-18 13:02 ` [Qemu-devel] [PATCH v2 2/2] pvpanic: fix fwcfg for big endian hosts Michael S. Tsirkin
2013-06-19 14:07 ` [Qemu-devel] [PATCH v2 1/2] pvpanic: initialization cleanup Laszlo Ersek
2013-06-19 14:13 ` Michael S. Tsirkin [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=20130619141303.GA5927@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=lersek@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).