linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Suraj Jitindar Singh <sjitindarsingh@gmail.com>,
	Paul Mackerras <paulus@ozlabs.org>,
	kvm@vger.kernel.org, linuxppc-dev@ozlabs.org,
	kvm-ppc@vger.kernel.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] KVM: PPC: Book3S: Add capabilities for Meltdown/Spectre workarounds
Date: Tue, 9 Jan 2018 13:54:53 +0100	[thread overview]
Message-ID: <20180109135453.28b36153@bahia.lan> (raw)
In-Reply-To: <2b9c6453-c56f-ac4d-daa9-16d9ffa6cebe@ozlabs.ru>

On Tue, 9 Jan 2018 23:44:56 +1100
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:

> On 09/01/18 19:39, Suraj Jitindar Singh wrote:
[...]
> >> +	rc = plpar_get_cpu_characteristics(&c);
> >> +	if (rc == H_SUCCESS) {
> >> +		if (!(c.behavior &   
> > 
> > s/behavior/behaviour  
> 
> Why?
> https://dictionary.cambridge.org/dictionary/english/behavior
> 

Behavior is US English while behaviour is UK (and US)... Matter of taste ? :)

> 
> 

  reply	other threads:[~2018-01-09 13:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  4:48 [PATCH] KVM: PPC: Book3S: Add capabilities for Meltdown/Spectre workarounds Paul Mackerras
2018-01-09  8:28 ` Suraj Jitindar Singh
2018-01-09  9:18   ` Paul Mackerras
2018-01-09  8:39 ` Suraj Jitindar Singh
2018-01-09 11:57   ` Michal Suchánek
2018-01-09 12:20     ` [PATCH] KVM: PPC: Book3S: Add capabilities for Meltdown/Spectre workarounds^[ joserz
2018-01-09 12:44   ` [PATCH] KVM: PPC: Book3S: Add capabilities for Meltdown/Spectre workarounds Alexey Kardashevskiy
2018-01-09 12:54     ` Greg Kurz [this message]
2018-01-09 14:36       ` Michael Ellerman
2018-01-10  0:59     ` Suraj Jitindar Singh
2018-01-09 11:54 ` kbuild test robot
2018-01-09 13:48 ` kbuild test robot

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=20180109135453.28b36153@bahia.lan \
    --to=groug@kaod.org \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@ozlabs.org \
    --cc=sjitindarsingh@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).