From: Mark Allyn <mark.a.allyn@intel.com>
To: linux-kernel@vger.kernel.org, greg@kroah.com,
alan@linux.intel.com, charles.f.johnson@intel.com
Cc: Mark Allyn <mark.a.allyn@intel.com>
Subject: [PATCH] Add reference to memrar.h file
Date: Mon, 18 Jan 2010 13:22:39 -0800 [thread overview]
Message-ID: <1263849759-23125-1-git-send-email-mark.a.allyn@intel.com> (raw)
The purpose of this patch is to add raference to memrar.h
This is the third of seven patches for the rar_register driver
for Sunday, January 17, 2009
The rar stands for restricted access region. The restricted access
region is an area of memory that can be locked from access by the
x86 processor.
The purpose of the restricted access region is to safeguard confidential
information from any unauthorized software running on the x86 processor.
The purpose of this driver is to enable other drivers to obtain
the address ranges of the restricted regions as well as lock them.
This patch is referenced off the linux-next repository as pulled
on Sunday, January 17th, 2010
Signed-off-by: Mark Allyn <mark.a.allyn@intel.com>
Date: January 17, 2010
---
drivers/staging/rar/rar_register.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/rar/rar_register.c b/drivers/staging/rar/rar_register.c
index 836d383..4b9a3a3 100644
--- a/drivers/staging/rar/rar_register.c
+++ b/drivers/staging/rar/rar_register.c
@@ -16,6 +16,7 @@
#include <linux/firmware.h>
#include <linux/sched.h>
#include <linux/rar/rar_register.h>
+#include <linux/rar/memrar.h>
/* The following defines are for the IPC process to retrieve RAR in */
--
1.6.0.6
next reply other threads:[~2010-01-18 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 21:22 Mark Allyn [this message]
2010-01-19 0:10 ` Greg KH
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=1263849759-23125-1-git-send-email-mark.a.allyn@intel.com \
--to=mark.a.allyn@intel.com \
--cc=alan@linux.intel.com \
--cc=charles.f.johnson@intel.com \
--cc=greg@kroah.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
all inboxes | Powered by JetHome®