From: David Gibson <david@gibson.dropbear.id.au>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Richard Henderson <richard.henderson@linaro.org>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Joe Komlodi <komlodi@xilinx.com>, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH] target/ppc: Remove unused MMU definitions
Date: Thu, 28 Jan 2021 11:22:31 +1100 [thread overview]
Message-ID: <20210128002231.GA18347@yekko.fritz.box> (raw)
In-Reply-To: <20210127232401.3525126-1-f4bug@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
On Thu, Jan 28, 2021 at 12:24:01AM +0100, Philippe Mathieu-Daudé wrote:
> Remove these confusing and unused definitions.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Applied to ppc-for-6.0.
> ---
> target/ppc/cpu.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/target/ppc/cpu.h b/target/ppc/cpu.h
> index 2609e4082ed..cb002102888 100644
> --- a/target/ppc/cpu.h
> +++ b/target/ppc/cpu.h
> @@ -2205,9 +2205,6 @@ enum {
> * may be needed for precise access rights control and precise exceptions.
> */
> enum {
> - /* 1 bit to define user level / supervisor access */
> - ACCESS_USER = 0x00,
> - ACCESS_SUPER = 0x01,
> /* Type of instruction that generated the access */
> ACCESS_CODE = 0x10, /* Code fetch access */
> ACCESS_INT = 0x20, /* Integer load/store access */
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-01-28 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 23:24 [PATCH] target/ppc: Remove unused MMU definitions Philippe Mathieu-Daudé
2021-01-28 0:22 ` David Gibson [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=20210128002231.GA18347@yekko.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=f4bug@amsat.org \
--cc=groug@kaod.org \
--cc=komlodi@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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).