public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Punit Vara <punitvara@gmail.com>
Cc: devel@driverdev.osuosl.org, arve@android.com,
	riandrews@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 	Staging: android: Fix 80 character length
Date: Fri, 18 Sep 2015 19:40:50 -0700	[thread overview]
Message-ID: <20150919024050.GA21258@kroah.com> (raw)
In-Reply-To: <1442566456-3647-1-git-send-email-punitvara@gmail.com>

On Fri, Sep 18, 2015 at 02:24:16PM +0530, Punit Vara wrote:
> 	This patch is to the Kconfig file which fixes up lines which
> 	exceeded the standard  80 character limitation.
> 	This file also fixes up 3 warnings regarding paragraph.

Why is this indented?

> 
> Signed-off-by: Punit Vara <punitvara@gmail.com>
> ---
>  drivers/staging/android/Kconfig | 28 ++++++++++++++++------------
>  1 file changed, 16 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/staging/android/Kconfig b/drivers/staging/android/Kconfig
> index 42b1512..f4a2371 100644
> --- a/drivers/staging/android/Kconfig
> +++ b/drivers/staging/android/Kconfig
> @@ -12,7 +12,8 @@ config ASHMEM
>  	  file-based API.
>  
>  	  It is, in theory, a good memory allocator for low-memory devices,
> -	  because it can discard shared memory units when under memory pressure.

This is 80 characters wide, no need to change it.

> +	  because it can discard shared memory units when under memory
> +	  pressure.
>  
>  config ANDROID_TIMED_OUTPUT
>  	bool "Timed output class driver"
> @@ -24,19 +25,20 @@ config ANDROID_TIMED_GPIO
>  	depends on ANDROID_TIMED_OUTPUT
>  	default n
>          ---help---
> -	  Unlike generic gpio is to allow programs to access and manipulate gpio
> -	  registers from user space, timed output/gpio is a system to allow changing
> -	  a gpio pin and restore it automatically after a specified timeout.
> +	  Unlike generic gpio is to allow programs to access and manipulate
> +	  gpio registers from user space, timed output/gpio is a system to
> +	  allow changing a gpio pin and restore it automatically after a
> +	  specified timeout.
>  
>  config ANDROID_LOW_MEMORY_KILLER
>  	bool "Android Low Memory Killer"
>  	---help---
> -	  Registers processes to be killed when low memory conditions, this is useful
> -	  as there is no particular swap space on android.
> +	  Registers processes to be killed when low memory conditions, this
> +	  is useful as there is no particular swap space on android.
>  
> -	  The registered process will kills according to the priorities in android init
> -	  scripts (/init.rc), and it defines priority values with minimum free memory size
> -	  for each priority.
> +	  The registered process will kills according to the priorities in
> +	  android init scripts (/init.rc), and it defines priority values with
> +	  minimum free memory size for each priority.
>  
>  config SYNC
>  	bool "Synchronization framework"
> @@ -44,8 +46,9 @@ config SYNC
>  	select ANON_INODES
>  	select DMA_SHARED_BUFFER
>  	---help---
> -	  This option enables the framework for synchronization between multiple

This is also ok.


> -	  drivers.  Sync implementations can take advantage of hardware
> +	  This option enables the framework for synchronization between
> +	  multiple drivers.
> +	  Sync implementations can take advantage of hardware
>  	  synchronization built into devices like GPUs.
>  
>  config SW_SYNC
> @@ -54,7 +57,8 @@ config SW_SYNC
>  	depends on SYNC
>  	---help---
>  	  A sync object driver that uses a 32bit counter to coordinate
> -	  synchronization.  Useful when there is no hardware primitive backing

And this is just fine, why change it?

thanks,

greg k-h

      reply	other threads:[~2015-09-19  4:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  8:54 [PATCH] Staging: android: Fix 80 character length Punit Vara
2015-09-19  2:40 ` Greg KH [this message]

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=20150919024050.GA21258@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=punitvara@gmail.com \
    --cc=riandrews@android.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