From: "Andreas Färber" <afaerber@suse.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] target-ppc: Use #define instead of opencoding SLB valid bit
Date: Mon, 19 Aug 2013 14:44:56 +0200 [thread overview]
Message-ID: <52121348.2090005@suse.de> (raw)
In-Reply-To: <1376915356-31011-3-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
Am 19.08.2013 14:29, schrieb Aneesh Kumar K.V:
> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
>
> Use SLB_ESID_V instead of (1 << 27) in the code
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Reviewed-by: Andreas Färber <afaerber@suse.de>
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-08-19 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 12:29 [Qemu-devel] [PATCH 0/3] target-ppc: Add support for dumping guest memory using qemu gdb server Aneesh Kumar K.V
2013-08-19 12:29 ` [Qemu-devel] [PATCH 1/3] target-ppc: Update slb array with correct index values Aneesh Kumar K.V
2013-08-19 12:42 ` Andreas Färber
2013-08-19 12:50 ` Andreas Färber
2013-08-19 12:29 ` [Qemu-devel] [PATCH 2/3] target-ppc: Use #define instead of opencoding SLB valid bit Aneesh Kumar K.V
2013-08-19 12:44 ` Andreas Färber [this message]
2013-08-19 12:29 ` [Qemu-devel] [PATCH 3/3] target-ppc: Fix page table lookup with kvm enabled Aneesh Kumar K.V
2013-08-19 13:07 ` Andreas Färber
2013-08-19 13:10 ` [Qemu-devel] [PATCH 0/3] target-ppc: Add support for dumping guest memory using qemu gdb server Andreas Färber
2013-08-20 8:19 ` Aneesh Kumar K.V
2013-08-20 12:49 ` Andreas Färber
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=52121348.2090005@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).