From: Blue Swirl <blauwirbel@gmail.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 01/14] Introduce qemu_write_full()
Date: Tue, 19 Jan 2010 18:50:09 +0000 [thread overview]
Message-ID: <f43fc5581001191050g49ce2e8dpc63964c07450710@mail.gmail.com> (raw)
In-Reply-To: <cc557aab1001190417l3976e667o925da73de054b0cb@mail.gmail.com>
On Tue, Jan 19, 2010 at 12:17 PM, Kirill A. Shutemov
<kirill@shutemov.name> wrote:
> On Tue, Jan 19, 2010 at 2:11 PM, Juan Quintela <quintela@redhat.com> wrote:
>> "Kirill A. Shutemov" <kirill@shutemov.name> wrote:
>>> A variant of write(2) which handles partial write.
>>>
>>> Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
>>
>> Hi
>>
>> Have you updated this series? Is there any reason that you know when
>> they haven't been picked?
>
> I don't know any reason, but I'm going to review it once again.
I don't know about others, but I didn't feel competent enough about
all possible corner cases of write().
> I also have plan to get rid of -fno-strict-aliasing where it's possible.
That should be interesting too, if it does not make code more unreadable.
next prev parent reply other threads:[~2010-01-19 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1262223199-19062-1-git-send-email-kirill@shutemov.name>
2010-01-19 12:11 ` [Qemu-devel] Re: [PATCH 01/14] Introduce qemu_write_full() Juan Quintela
2010-01-19 12:17 ` Kirill A. Shutemov
2010-01-19 18:50 ` Blue Swirl [this message]
2010-01-19 19:43 ` Anthony Liguori
2010-01-20 0:04 ` Juan Quintela
2010-01-20 1:04 ` Anthony Liguori
2010-01-20 1:30 ` Jamie Lokier
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=f43fc5581001191050g49ce2e8dpc63964c07450710@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=kirill@shutemov.name \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).