From: joserz@linux.vnet.ibm.com
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] KVM: PPC: Book3S: Add capabilities for Meltdown/Spectre workarounds^[
Date: Tue, 9 Jan 2018 10:20:04 -0200 [thread overview]
Message-ID: <20180109122004.gaskxr67feftftsw@pacoca> (raw)
In-Reply-To: <20180109125726.39687794@kitsune.suse.cz>
On Tue, Jan 09, 2018 at 12:57:26PM +0100, Michal Suchánek wrote:
> On Tue, 09 Jan 2018 19:39:14 +1100
> Suraj Jitindar Singh <sjitindarsingh@gmail.com> wrote:
>
> >
> > s/behavior/behaviour
>
> Nope. Either is valid and the shorter American spelling is actually
> more common.
>
> If you must nickpick choose something actually broken :p
Suraj is right:
struct h_cpu_char_result {
u64 character;
u64 behaviour;
};
>
> Thanks
>
> Michal
>
next prev parent reply other threads:[~2018-01-09 12:20 UTC|newest]
Thread overview: 24+ 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 4:48 ` Paul Mackerras
2018-01-09 8:28 ` Suraj Jitindar Singh
2018-01-09 8:28 ` Suraj Jitindar Singh
2018-01-09 9:18 ` Paul Mackerras
2018-01-09 9:18 ` Paul Mackerras
2018-01-09 8:39 ` Suraj Jitindar Singh
2018-01-09 8:39 ` Suraj Jitindar Singh
2018-01-09 11:57 ` Michal Suchánek
2018-01-09 12:20 ` joserz [this message]
2018-01-09 12:44 ` Alexey Kardashevskiy
2018-01-09 12:44 ` Alexey Kardashevskiy
2018-01-09 12:54 ` Greg Kurz
2018-01-09 12:54 ` Greg Kurz
2018-01-09 12:54 ` Greg Kurz
2018-01-09 14:36 ` Michael Ellerman
2018-01-09 14:36 ` Michael Ellerman
2018-01-09 14:36 ` Michael Ellerman
2018-01-10 0:59 ` Suraj Jitindar Singh
2018-01-10 0:59 ` Suraj Jitindar Singh
2018-01-09 11:54 ` kbuild test robot
2018-01-09 11:54 ` kbuild test robot
2018-01-09 13:48 ` 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=20180109122004.gaskxr67feftftsw@pacoca \
--to=joserz@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
/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.