From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, Jean-Christophe Dubois <jcd@tribudubois.net>
Subject: Re: [Qemu-devel] [PATCH v4] avoid compilation warning/errors on up to date
Date: Thu, 18 Jun 2009 15:33:03 -0500 [thread overview]
Message-ID: <4A3AA47F.9090004@codemonkey.ws> (raw)
In-Reply-To: <20090618171639.1a3c1364@doriath>
Luiz Capitulino wrote:
> On Thu, 18 Jun 2009 01:16:37 +0200
> "Jean-Christophe Dubois" <jcd@tribudubois.net> wrote:
>
>
>> And whatever I have added is a lot more robust than what was before.
>> Once again, please just show me where my patch is incorrect and I
>> will fix it.
>>
>
> I really missed this v4, sorry for that and thanks for letting me know.
>
> I think the first step is to do one logical change at a time. You
> could, for example do:
>
> 1. Add qemu_read() and qemu_write()
>
We already have these in various places. The problem is, we often want
different semantics. We don't always want to retry partial results
(like for live migration). We need a more rationalized approach to this.
> 2. Port one subsystem per-patch for each of them
>
Yes, and for each fixup, fix the whole function, not just a handful of
functions that gcc currently whines about.
N.B. I will be pushing -U_FORTIFY_SOURCE so the ubuntu build breakage
will be fixed. We have the time to fix these warnings correctly.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-06-18 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 21:22 [Qemu-devel] [PATCH v4] avoid compilation warning/errors on up to date Jean-Christophe Dubois
2009-06-17 21:51 ` malc
2009-06-17 22:58 ` Jean-Christophe Dubois
2009-06-18 1:17 ` malc
2009-06-17 21:54 ` Anthony Liguori
2009-06-17 22:41 ` Jean-Christophe Dubois
2009-06-17 22:51 ` Anthony Liguori
2009-06-17 23:16 ` Jean-Christophe Dubois
2009-06-18 20:16 ` Luiz Capitulino
2009-06-18 20:33 ` Anthony Liguori [this message]
2009-06-18 21:05 ` Luiz Capitulino
2009-06-18 21:10 ` Jean-Christophe Dubois
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=4A3AA47F.9090004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jcd@tribudubois.net \
--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.