From: "Andreas Färber" <afaerber@suse.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Stefan Weil <sw@weilnetz.de>, Richard Henderson <rth@twiddle.net>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/4] exec: prepare for splitting
Date: Tue, 01 May 2012 13:50:07 +0200 [thread overview]
Message-ID: <4F9FCDEF.2050908@suse.de> (raw)
In-Reply-To: <CAAu8pHusruwVf6U0vrYa8DQ9+8PbcEs85TxyDEBYUGCQK68_sA@mail.gmail.com>
Am 01.05.2012 13:47, schrieb Blue Swirl:
> On Tue, May 1, 2012 at 11:02, Andreas Färber <afaerber@suse.de> wrote:
>> Am 22.04.2012 17:35, schrieb Blue Swirl:
>>> Make s_cputlb_empty_entry 'const'.
>>>
>>> Rename tlb_flush_jmp_cache() to tb_flush_jmp_cache().
>>>
>>> Refactor code to add cpu_tlb_reset_dirty_all(),
>>> memory_region_section_get_iotlb() and
>>> memory_region_is_unassigned().
>>>
>>> Remove unused cpu_tlb_update_dirty().
>>>
>>> Fix coding style in areas to be moved.
>>>
>>> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
>>
>> This patch is line-wrapped. It's even worse on Patchwork. I fixed the
>> mail up and applied it manually with fuzz (the exec.c 46xx hunk).
>>
>> Compiles fine on openSUSE 12.1 x86_64, and so do mingw32 and mingw64
>> cross builds.
>>
>> Tested-by: Andreas Färber <afaerber@suse.de>
>
> Thanks for testing, though I could not insert the tag anymore, sorry.
> I applied the series.
Then I'll stop building the second one. ;)
/-F
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-05-01 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAu8pHvtVHxcDznCFaRHqHLhLuEz8d58jYCm59UK5Fz9-Ljpdg@mail.gmail.com>
2012-05-01 11:02 ` [Qemu-devel] [PATCH 1/4] exec: prepare for splitting Andreas Färber
2012-05-01 11:47 ` Blue Swirl
2012-05-01 11:50 ` Andreas Färber [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=4F9FCDEF.2050908@suse.de \
--to=afaerber@suse.de \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sw@weilnetz.de \
/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.