From: Paolo Bonzini <pbonzini@redhat.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
kvm@vger.kernel.org, Sanjay Lal <sanjayl@kymasys.com>,
Gleb Natapov <gleb@redhat.com>,
linux-kernel@vger.kernel.org,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH 0/3] mips/kvm: Code cleanups for kvm_locore.S
Date: Fri, 09 Aug 2013 13:50:14 +0200 [thread overview]
Message-ID: <5204D776.6040903@redhat.com> (raw)
In-Reply-To: <1375388555-4045-1-git-send-email-ddaney.cavm@gmail.com>
Il 01/08/2013 22:22, David Daney ha scritto:
> From: David Daney <david.daney@cavium.com>
>
> These shouldn't be too controversial, they just clean things up
> without changing the generated code.
>
> More substantial patches will follow, but it seemed like a good idea
> to clean this up first.
>
> David Daney (3):
> mips/kvm: Improve code formatting in arch/mips/kvm/kvm_locore.S
> mips/kvm: Cleanup .push/.pop directives in kvm_locore.S
> mips/kvm: Make kvm_locore.S 64-bit buildable/safe.
>
> arch/mips/kvm/kvm_locore.S | 965 ++++++++++++++++++++++-----------------------
> 1 file changed, 480 insertions(+), 485 deletions(-)
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
prev parent reply other threads:[~2013-08-09 11:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 20:22 [PATCH 0/3] mips/kvm: Code cleanups for kvm_locore.S David Daney
2013-08-01 20:22 ` [PATCH 1/3] mips/kvm: Improve code formatting in arch/mips/kvm/kvm_locore.S David Daney
2013-08-05 13:17 ` James Hogan
2013-08-05 13:21 ` Ralf Baechle
2013-08-05 13:43 ` Gleb Natapov
2013-08-05 16:52 ` David Daney
2013-08-05 17:06 ` Ralf Baechle
2013-08-05 17:22 ` Gleb Natapov
2013-08-01 20:22 ` [PATCH 2/3] mips/kvm: Cleanup .push/.pop directives in kvm_locore.S David Daney
2013-08-01 20:22 ` [PATCH 3/3] mips/kvm: Make kvm_locore.S 64-bit buildable/safe David Daney
2013-08-09 11:50 ` Paolo Bonzini [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=5204D776.6040903@redhat.com \
--to=pbonzini@redhat.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sanjayl@kymasys.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).