From: Ralf Baechle <ralf@linux-mips.org>
To: Sanjay Lal <sanjayl@kymasys.com>
Cc: kvm@vger.kernel.org, linux-mips@linux-mips.org, gleb@redhat.com,
mtosatti@redhat.com
Subject: Re: [PATCH 3/3] KVM/MIPS32: Fix up KVM breakage caused by d532f3d26716a39dfd4b88d687bd344fbe77e390 which allows ASID mask and increment to be determined @ runtime.
Date: Sat, 18 May 2013 02:06:36 +0200 [thread overview]
Message-ID: <20130518000636.GC24568@linux-mips.org> (raw)
In-Reply-To: <1368825912-23562-4-git-send-email-sanjayl@kymasys.com>
On Fri, May 17, 2013 at 02:25:12PM -0700, Sanjay Lal wrote:
> Date: Fri, 17 May 2013 14:25:12 -0700
> From: Sanjay Lal <sanjayl@kymasys.com>
> To: kvm@vger.kernel.org
> Cc: linux-mips@linux-mips.org, ralf@linux-mips.org, gleb@redhat.com,
> mtosatti@redhat.com, Sanjay Lal <sanjayl@kymasys.com>
> Subject: [PATCH 3/3] KVM/MIPS32: Fix up KVM breakage caused by
> d532f3d26716a39dfd4b88d687bd344fbe77e390 which allows ASID mask and
> increment to be determined @ runtime.
Good grief, yet another bug report against that patch ... I've reverted
d532f3d26 just before your posting. So I'm going to drop this patch.
Thanks,
Ralf
next prev parent reply other threads:[~2013-05-18 0:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 21:25 [PATCH v2 0/3] KVM/MIPS32: Fixes for Linux 3.10 Sanjay Lal
2013-05-17 21:25 ` [PATCH 1/3] KVM/MIPS32: Move include/asm/kvm.h => include/uapi/asm/kvm.h since it is a user visible API Sanjay Lal
2013-05-17 21:25 ` [PATCH 2/3] KVM/MIPS32: Wrap calls to gfn_to_pfn() with srcu_read_lock/unlock() Sanjay Lal
2013-05-18 6:21 ` Gleb Natapov
2013-05-17 21:25 ` [PATCH 3/3] KVM/MIPS32: Fix up KVM breakage caused by d532f3d26716a39dfd4b88d687bd344fbe77e390 which allows ASID mask and increment to be determined @ runtime Sanjay Lal
2013-05-18 0:06 ` Ralf Baechle [this message]
2013-05-18 6:23 ` Gleb Natapov
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=20130518000636.GC24568@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mtosatti@redhat.com \
--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