public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/1] intel txt: Fix typos in Kconfig help
Date: Wed, 12 Aug 2009 12:00:40 -0300	[thread overview]
Message-ID: <20090812150040.GH3180@ghostprotocols.net> (raw)

Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 security/Kconfig |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/security/Kconfig b/security/Kconfig
index edc7cbd..6631774 100644
--- a/security/Kconfig
+++ b/security/Kconfig
@@ -123,7 +123,7 @@ config INTEL_TXT
 	  of the kernel. If the system does not support Intel(R) TXT, this
 	  will have no effect.
 
-	  Intel TXT will provide higher assurance of sysem configuration and
+	  Intel TXT will provide higher assurance of system configuration and
 	  initial state as well as data reset protection.  This is used to
 	  create a robust initial kernel measurement and verification, which
 	  helps to ensure that kernel security mechanisms are functioning
@@ -132,7 +132,7 @@ config INTEL_TXT
 
 	  Intel TXT also helps solve real end user concerns about having
 	  confidence that their hardware is running the VMM or kernel that
-	  it was conigured with, especially since they may be responsible for
+	  it was configured with, especially since they may be responsible for
 	  providing such assurances to VMs and services running on it.
 
 	  See <http://www.intel.com/technology/security/> for more information
-- 
1.6.2.5



             reply	other threads:[~2009-08-12 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 15:00 Arnaldo Carvalho de Melo [this message]
2009-08-14 23:43 ` [PATCH 1/1] intel txt: Fix typos in Kconfig help H. Peter Anvin

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=20090812150040.GH3180@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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