From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: stefano.stabellini@eu.citrix.com, marcel.a@redhat.com,
agraf@suse.de, qemu-devel@nongnu.org, pbonzini@redhat.com,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH 2/4] vl.c: use single local_err throughout main()
Date: Wed, 25 Jun 2014 14:16:20 +0200 [thread overview]
Message-ID: <20140625141620.2832891e@nial.usersys.redhat.com> (raw)
In-Reply-To: <20140625115152.GB13690@redhat.com>
On Wed, 25 Jun 2014 14:51:52 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Jun 25, 2014 at 01:42:21PM +0200, Igor Mammedov wrote:
> > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
>
> Fixes any bugs?
Nope, it's to reduce code duplication, which would be increased
in following patch.
>
> > ---
> > vl.c | 4 +---
> > 1 files changed, 1 insertions(+), 3 deletions(-)
> >
> > diff --git a/vl.c b/vl.c
> > index 6b09220..0a39c93 100644
> > --- a/vl.c
> > +++ b/vl.c
> > @@ -2927,6 +2927,7 @@ int main(int argc, char **argv, char **envp)
> > };
> > const char *trace_events = NULL;
> > const char *trace_file = NULL;
> > + Error *local_err = NULL;
> > const ram_addr_t default_ram_size = (ram_addr_t)DEFAULT_RAM_SIZE *
> > 1024 * 1024;
> > ram_addr_t maxram_size = default_ram_size;
> > @@ -4220,7 +4221,6 @@ int main(int argc, char **argv, char **envp)
> > configure_accelerator(machine_class);
> >
> > if (qtest_chrdev) {
> > - Error *local_err = NULL;
> > qtest_init(qtest_chrdev, qtest_log, &local_err);
> > if (local_err) {
> > error_report("%s", error_get_pretty(local_err));
> > @@ -4448,7 +4448,6 @@ int main(int argc, char **argv, char **envp)
> > #ifdef CONFIG_VNC
> > /* init remote displays */
> > if (vnc_display) {
> > - Error *local_err = NULL;
> > vnc_display_init(ds);
> > vnc_display_open(ds, vnc_display, &local_err);
> > if (local_err != NULL) {
> > @@ -4503,7 +4502,6 @@ int main(int argc, char **argv, char **envp)
> > }
> >
> > if (incoming) {
> > - Error *local_err = NULL;
> > qemu_start_incoming_migration(incoming, &local_err);
> > if (local_err) {
> > error_report("-incoming %s: %s", incoming,
> > --
> > 1.7.1
>
next prev parent reply other threads:[~2014-06-25 12:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 11:42 [Qemu-devel] [PATCH 0/4] tests for -m option Igor Mammedov
2014-06-25 11:42 ` [Qemu-devel] [PATCH 1/4] switch RAM_ADDR_FMT format specifier to print decimal Igor Mammedov
2014-06-25 11:51 ` Michael S. Tsirkin
2014-06-25 12:14 ` Igor Mammedov
2014-06-25 15:38 ` Michael S. Tsirkin
2014-06-25 17:47 ` Peter Maydell
2014-06-25 11:42 ` [Qemu-devel] [PATCH 2/4] vl.c: use single local_err throughout main() Igor Mammedov
2014-06-25 11:51 ` Michael S. Tsirkin
2014-06-25 12:16 ` Igor Mammedov [this message]
2014-06-25 15:42 ` Michael S. Tsirkin
2014-06-25 11:42 ` [Qemu-devel] [PATCH 3/4] machine: convert ram_size, maxram_size, ram_slots to properties Igor Mammedov
2014-06-25 11:54 ` Michael S. Tsirkin
2014-06-25 13:08 ` Igor Mammedov
2014-06-25 15:37 ` Michael S. Tsirkin
2014-06-25 14:09 ` Kirill Batuzov
2014-06-25 14:45 ` Igor Mammedov
2014-06-25 11:42 ` [Qemu-devel] [PATCH 4/4] test -m option parameters Igor Mammedov
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=20140625141620.2832891e@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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).