From: Juan Quintela <quintela@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: balrog@zabor.org, i.mitsyanko@samsung.com, qemu-devel@nongnu.org,
paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH 1/7] vmware_vga: port to test_and_clear instead of test/reset
Date: Fri, 11 Oct 2013 17:10:27 +0200 [thread overview]
Message-ID: <87li1zj124.fsf@elfo.elfo> (raw)
In-Reply-To: <52580DD7.8030700@redhat.com> (Eric Blake's message of "Fri, 11 Oct 2013 08:40:23 -0600")
Eric Blake <eblake@redhat.com> wrote:
> On 10/11/2013 08:20 AM, Juan Quintela wrote:
>> From: Juan Quintela <quintela@trasno.org>
>>
>> I am assuming that we are testing all the device pages on the loop,
>> that is right?
>>
>> Signed-off-by: Juan Quintela <quintela@trasno.org>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>
> Double S-o-B throughout the series looks a bit odd. Might be worth
> using just a preferred address?
Fixed locally just after send.
Setup is that repositories by default get my local address, and then I
switched them to my redhat one for the official ones. Clearly, my
memory failed me here. Sorry :-(
next prev parent reply other threads:[~2013-10-11 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 14:20 [Qemu-devel] [PATCH 0/7] Make vga devices use test_and_set Juan Quintela
2013-10-11 14:20 ` [Qemu-devel] [PATCH 1/7] vmware_vga: port to test_and_clear instead of test/reset Juan Quintela
2013-10-11 14:40 ` Eric Blake
2013-10-11 15:10 ` Juan Quintela [this message]
2013-10-11 14:20 ` [Qemu-devel] [PATCH 2/7] vga: " Juan Quintela
2013-10-11 14:20 ` [Qemu-devel] [PATCH 3/7] tcx: " Juan Quintela
2013-10-11 14:20 ` [Qemu-devel] [PATCH 4/7] sm501: " Juan Quintela
2013-10-11 14:20 ` [Qemu-devel] [PATCH 5/7] g364fb: " Juan Quintela
2013-10-11 14:20 ` [Qemu-devel] [PATCH 6/7] framebufer: " Juan Quintela
2013-10-11 14:20 ` [Qemu-devel] [PATCH 7/7] exynox4210: " Juan Quintela
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=87li1zj124.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=balrog@zabor.org \
--cc=eblake@redhat.com \
--cc=i.mitsyanko@samsung.com \
--cc=paul@codesourcery.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.