Re: [PATCH 2/2] Kconfig cleanup - new.

[Randy Dunlap <randy.dunlap@oracle.com>]

Matt LaPlante wrote:
> These are new kconfig cleanups, as of 2.6.29-rc2.

I only reviewed the new patch since you said that the other one had
already been approved.

> Not yet reviewed.
> 
> Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
> ---
>  arch/avr32/Kconfig                  |    6 +++---
>  drivers/hid/Kconfig                 |    2 +-
>  drivers/isdn/mISDN/Kconfig          |   10 ++++++----
>  drivers/media/common/tuners/Kconfig |    2 +-
>  drivers/mfd/Kconfig                 |    2 +-
>  drivers/mmc/host/Kconfig            |    2 +-
>  drivers/scsi/Kconfig                |    4 ++--
>  drivers/staging/Kconfig             |    4 ++--
>  drivers/staging/comedi/Kconfig      |    4 ++--
>  drivers/staging/go7007/Kconfig      |    4 ++--
>  drivers/staging/panel/Kconfig       |    2 +-
>  drivers/usb/gadget/Kconfig          |    2 +-
>  drivers/uwb/Kconfig                 |    4 ++--
>  drivers/xen/Kconfig                 |    2 +-
>  fs/Kconfig                          |    2 +-
>  fs/ext4/Kconfig                     |    2 +-
>  fs/ubifs/Kconfig                    |    4 ++--
>  init/Kconfig                        |    2 +-
>  kernel/trace/Kconfig                |    9 ++++-----
>  net/phonet/Kconfig                  |    2 +-
>  net/wimax/Kconfig                   |    2 +-
>  sound/soc/blackfin/Kconfig          |    2 +-
>  22 files changed, 38 insertions(+), 37 deletions(-)


> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index e2a4ff6..d85ab89 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -71,11 +71,10 @@ config FUNCTION_GRAPH_TRACER
>  	help
>  	  Enable the kernel to trace a function at both its return
>  	  and its entry.
> -	  It's first purpose is to trace the duration of functions and
> -	  draw a call graph for each thread with some informations like
> -	  the return value.
> -	  This is done by setting the current return address on the current
> -	  task structure into a stack of calls.
> +	  Its first purpose is to trace the duration of functions and
> +	  draw a call graph for each thread with some information like
> +	  the return value. This is done by setting the current return 
> +    address on the current task structure into a stack of calls.

spacing typo.
Fix that & add:
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>

>  
>  config IRQSOFF_TRACER
>  	bool "Interrupts-off Latency Tracer"


Thanks,
-- 
~Randy