From: Chris Smart <chris@distroguy.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Add support for userspace P9 copy paste
Date: Tue, 26 Apr 2016 16:49:57 +1000 [thread overview]
Message-ID: <20160426064956.GA14834@distroguy.com> (raw)
In-Reply-To: <20160426164209.7c28ca8c@camb691>
On Tue, Apr 26, 2016 at 04:42:09PM +1000, Cyril Bur wrote:
>Hi Chris,
>
>Patch looks good. Looks like you've put 8 spaces (instead of a tab) on the
>PPC_CP_ABORT line.
>
Argh. I'm not sure how that happened, thanks.
>Apart from that,
>
>Reviewed-by: Cyril Bur <cyrilbur@gmail.com>
Cheers,
-c
next prev parent reply other threads:[~2016-04-26 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 0:28 [PATCH] powerpc: Add support for userspace P9 copy paste Chris Smart
2016-04-26 6:42 ` Cyril Bur
2016-04-26 6:49 ` Chris Smart [this message]
2016-04-26 7:45 ` Balbir Singh
2016-04-27 2:05 ` Michael Neuling
2016-04-27 15:25 ` David Laight
2016-04-27 23:51 ` Chris Smart
2016-04-28 14:48 ` David Laight
2016-04-28 14:22 ` Michael Ellerman
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=20160426064956.GA14834@distroguy.com \
--to=chris@distroguy.com \
--cc=linuxppc-dev@lists.ozlabs.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).