From: mark gross <mgross@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: doc fix
Date: Thu, 23 Apr 2020 09:38:31 -0700 [thread overview]
Message-ID: <20200423163831.GA90742@mtg-dev.jf.intel.com> (raw)
In-Reply-To: <20200422203506.fks53pgkuq5tawdu@treble>
On Wed, Apr 22, 2020 at 03:35:06PM -0500, speck for Josh Poimboeuf wrote:
> From: Josh Poimboeuf <jpoimboe@redhat.com>
> Subject: [PATCH] x86/speculation: Add Ivy Bridge to affected list
>
> Make the docs match the code.
>
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
> ---
> .../hw-vuln/special-register-buffer-data-sampling.rst | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst b/Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst
> index 6a473da80b62..47b1b3afac99 100644
> --- a/Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst
> +++ b/Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst
> @@ -27,6 +27,8 @@ by software using TSX_CTRL_MSR otherwise they are not affected.
> ============= ============ ========
> common name Family_Model Stepping
> ============= ============ ========
> + IvyBridge 06_3AH All
> +
> Haswell 06_3CH All
> Haswell_L 06_45H All
> Haswell_G 06_46H All
> @@ -37,9 +39,8 @@ by software using TSX_CTRL_MSR otherwise they are not affected.
> Skylake_L 06_4EH All
> Skylake 06_5EH All
>
> - Kabylake_L 06_8EH <=0xC
> -
> - Kabylake 06_9EH <=0xD
> + Kabylake_L 06_8EH <= 0xC
> + Kabylake 06_9EH <= 0xD
> ============= ============ ========
>
> Related CVEs
> --
> 2.21.1
looks good to me.
--mark
next prev parent reply other threads:[~2020-04-23 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 20:35 [MODERATED] doc fix Josh Poimboeuf
2020-04-23 16:38 ` mark gross [this message]
2020-04-27 15:35 ` [MODERATED] " Josh Poimboeuf
2020-04-27 19:12 ` Thomas Gleixner
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=20200423163831.GA90742@mtg-dev.jf.intel.com \
--to=mgross@linux.intel.com \
--cc=speck@linutronix.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 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).