From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: powerpc/64s: tidy up after exception handler rework
Date: Fri, 10 Feb 2017 00:17:50 +1100 (AEDT) [thread overview]
Message-ID: <3vJzCL3twsz9s7N@ozlabs.org> (raw)
In-Reply-To: <20161206014015.10937-1-npiggin@gmail.com>
On Tue, 2016-12-06 at 01:40:15 UTC, Nicholas Piggin wrote:
> Somewhere along the line, search/replace left some naming garbled,
> and untidy alignment. Might as well fix them all up now while git
> blame history doesn't extend too far.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/852e5da99d15d0631c09e718abaa4b
cheers
prev parent reply other threads:[~2017-02-09 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 1:40 [PATCH] powerpc/64s: tidy up after exception handler rework Nicholas Piggin
2017-02-09 13:17 ` Michael Ellerman [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=3vJzCL3twsz9s7N@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).