From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com
Subject: [Qemu-devel] [qemu-web PATCH] spectre blog post: I accidentally a verb
Date: Tue, 9 Jan 2018 09:37:04 +0100 [thread overview]
Message-ID: <20180109083704.24075-1-pbonzini@redhat.com> (raw)
Reported-by: Fam Zheng <famz@redhat.com>
---
_posts/2018-01-04-spectre.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_posts/2018-01-04-spectre.md b/_posts/2018-01-04-spectre.md
index 353ac7c..aa0f5e4 100644
--- a/_posts/2018-01-04-spectre.md
+++ b/_posts/2018-01-04-spectre.md
@@ -60,7 +60,7 @@ Because the virtual CPU has to be changed to one with the new CPUID bits,
the guest will have to be restarted.
As of today, the QEMU project is not aware of whether similar changes will
-be required for non-x86 processors. If so, they will also posted to the
+be required for non-x86 processors. If so, they will also be posted to the
mailing list and backported to recent stable releases.
For more information on the vulnerabilities, please refer to the [Google Security
--
2.14.3
reply other threads:[~2018-01-09 8:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180109083704.24075-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.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).