linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: paulus@samba.org, anton@samba.org, npiggin@gmail.com
Subject: Re: [01/16] powerpc/64s: Move SET_SCRATCH0() into EXCEPTION_PROLOG_PSERIES()
Date: Thu,  9 Aug 2018 00:26:07 +1000 (AEST)	[thread overview]
Message-ID: <41ltwl1LHXz9s8W@ozlabs.org> (raw)
In-Reply-To: <20180726130717.18761-2-mpe@ellerman.id.au>

On Thu, 2018-07-26 at 13:07:02 UTC, Michael Ellerman wrote:
> EXCEPTION_PROLOG_PSERIES() only has two users, STD_EXCEPTION_PSERIES()
> and STD_EXCEPTION_HV() both of which "call" SET_SCRATCH0(), so just
> move SET_SCRATCH0() into EXCEPTION_PROLOG_PSERIES().
> 
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>

Series applied to powerpc next.

https://git.kernel.org/powerpc/c/4a7a0a8444ba4cebb3a6744e9c14fc

cheers

  reply	other threads:[~2018-08-08 14:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 13:07 [PATCH 00/16] Finally remove PSERIES from exception naming Michael Ellerman
2018-07-26 13:07 ` [PATCH 01/16] powerpc/64s: Move SET_SCRATCH0() into EXCEPTION_PROLOG_PSERIES() Michael Ellerman
2018-08-08 14:26   ` Michael Ellerman [this message]
2018-07-26 13:07 ` [PATCH 02/16] powerpc/64s: Move SET_SCRATCH0() into EXCEPTION_RELON_PROLOG_PSERIES() Michael Ellerman
2018-07-26 13:07 ` [PATCH 03/16] powerpc/64s: Rename STD_EXCEPTION_PSERIES to STD_EXCEPTION Michael Ellerman
2018-07-26 13:07 ` [PATCH 04/16] powerpc/64s: Rename STD_EXCEPTION_PSERIES_OOL to STD_EXCEPTION_OOL Michael Ellerman
2018-07-26 13:07 ` [PATCH 05/16] powerpc/64s: Rename STD_RELON_EXCEPTION_PSERIES to STD_RELON_EXCEPTION Michael Ellerman
2018-07-26 13:07 ` [PATCH 06/16] powerpc/64s: Rename STD_RELON_EXCEPTION_PSERIES_OOL to STD_RELON_EXCEPTION_OOL Michael Ellerman
2018-07-26 13:07 ` [PATCH 07/16] powerpc/64s: Rename EXCEPTION_PROLOG_PSERIES_1 to EXCEPTION_PROLOG_2 Michael Ellerman
2018-07-26 13:07 ` [PATCH 08/16] powerpc/64s: Remove PSERIES from the NORI macros Michael Ellerman
2018-07-26 13:07 ` [PATCH 09/16] powerpc/64s: Rename EXCEPTION_RELON_PROLOG_PSERIES_1 Michael Ellerman
2018-07-26 13:07 ` [PATCH 10/16] powerpc/64s: Rename EXCEPTION_RELON_PROLOG_PSERIES Michael Ellerman
2018-07-26 13:07 ` [PATCH 11/16] powerpc/64s: Rename EXCEPTION_PROLOG_PSERIES to EXCEPTION_PROLOG Michael Ellerman
2018-07-26 13:07 ` [PATCH 12/16] powerpc/64s: Drop _MASKABLE_EXCEPTION_PSERIES() Michael Ellerman
2018-07-26 13:07 ` [PATCH 13/16] powerpc/64s: Drop _MASKABLE_RELON_EXCEPTION_PSERIES() Michael Ellerman
2018-07-26 13:07 ` [PATCH 14/16] powerpc/64s: Remove PSERIES naming from the MASKABLE macros Michael Ellerman
2018-07-26 13:07 ` [PATCH 15/16] powerpc/64s: Drop unused loc parameter to MASKABLE_EXCEPTION macros Michael Ellerman
2018-07-26 13:07 ` [PATCH 16/16] powerpc/64s: Don't use __MASKABLE_EXCEPTION unnecessarily Michael Ellerman
2018-08-01  2:12 ` [PATCH 00/16] Finally remove PSERIES from exception naming Nicholas Piggin

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=41ltwl1LHXz9s8W@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.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).