All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Neuling <mikey@neuling.org>
Cc: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc: Document issues with the DAWR on POWER9
Date: Fri, 22 Jun 2018 12:23:09 -0500	[thread overview]
Message-ID: <20180622172308.GQ16221@gate.crashing.org> (raw)
In-Reply-To: <20180622061452.19016-1-mikey@neuling.org>

On Fri, Jun 22, 2018 at 04:14:51PM +1000, Michael Neuling wrote:
> +will accept the command. Unfortunatley since there is no hardware

"unfortunately".

> +speed since it can use the hardware emualation. Unfortnatley if this

It is not your favourite word to type ;-)


Segher

  parent reply	other threads:[~2018-06-22 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  6:14 [PATCH 1/2] powerpc: Document issues with the DAWR on POWER9 Michael Neuling
2018-06-22  6:14 ` [PATCH 2/2] powerpc: Document issues with TM " Michael Neuling
2018-06-22  7:01   ` Stewart Smith
2018-06-22 17:27   ` Segher Boessenkool
2018-06-22  7:00 ` [PATCH 1/2] powerpc: Document issues with the DAWR " Stewart Smith
2018-06-22 17:23 ` Segher Boessenkool [this message]
2018-06-25  1:30   ` Michael Neuling

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=20180622172308.GQ16221@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=mpe@ellerman.id.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.