mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Mark Allyn <mark.a.allyn@intel.com>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
	alan@linux.intel.com, charles.f.johnson@intel.com
Subject: Re: [PATCH] Remove cflags from Makefile and fix Kconfig
Date: Mon, 18 Jan 2010 15:31:07 -0800	[thread overview]
Message-ID: <20100118153107.567b2b0c.rdunlap@xenotime.net> (raw)
In-Reply-To: <1263849774-23152-1-git-send-email-mark.a.allyn@intel.com>

On Mon, 18 Jan 2010 13:22:54 -0800 Mark Allyn wrote:

> This patch fixes bothe the Makefile and the Kconfig file
> 
> This is the fourth 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 17, 2010
> 
> Signed-off-by: Mark Allyn <mark.a.allyn@intel.com>
> 
> Date: January 17, 2010
> ---
>  drivers/staging/rar/Kconfig  |    8 ++++++--
>  drivers/staging/rar/Makefile |    1 -
>  2 files changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/rar/Kconfig b/drivers/staging/rar/Kconfig
> index 17f8bf3..e923178 100644
> --- a/drivers/staging/rar/Kconfig
> +++ b/drivers/staging/rar/Kconfig
> @@ -8,10 +8,14 @@ menu "RAR Register Driver"
>  #
>  config RAR_REGISTER
>  	tristate "Restricted Access Region Register Driver"
> -	default n
>  	---help---
>  		This driver allows other kernel drivers access to the
>  		contents of the restricted access region control
> -		registers.
> +		registers. The restricted access regions are areas
> +		of memory on the Intel ultra mobile platform which the
> +		x86 processor (and software running thereupon) cannot
> +		access for reading or writing. It is used the protect
		                                          ^^^
		                                          to

> +		sensitive information from unauthorized programms running
> +		on the x86 processor.
>  
>  endmenu
> diff --git a/drivers/staging/rar/Makefile b/drivers/staging/rar/Makefile
> index d5954cc..7f1478b 100644
> --- a/drivers/staging/rar/Makefile
> +++ b/drivers/staging/rar/Makefile
> @@ -1,2 +1 @@
> -EXTRA_CFLAGS += -DLITTLE__ENDIAN
>  obj-$(CONFIG_RAR_REGISTER) += rar_register.o
> -- 
> 1.6.0.6
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


---
~Randy

  reply	other threads:[~2010-01-18 23:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 21:22 Mark Allyn
2010-01-18 23:31 ` Randy Dunlap [this message]
2010-01-19  0:13 ` 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=20100118153107.567b2b0c.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=alan@linux.intel.com \
    --cc=charles.f.johnson@intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.a.allyn@intel.com \
    /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®