public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yi Yang <yang.y.yi@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [2.6.16 PATCH] some tail whitespace clean under subdirectory kernel
Date: Thu, 23 Mar 2006 09:05:53 +0800	[thread overview]
Message-ID: <4421F471.3030505@gmail.com> (raw)
In-Reply-To: <44219917.90806@gmail.com>

Jiri Slaby wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Yi Yang napsal(a):
>   
>> This patch cleans some tail whitespaces under subdirectory kernel.
>>
>>
>> diffstat
>>  capability.c |   20 ++++++++++----------
>>  fork.c       |   12 ++++++------
>>  signal.c     |   14 +++++++-------
>>  sys.c        |   38 +++++++++++++++++++-------------------
>>  timer.c      |   18 +++++++++---------
>>  5 files changed, 51 insertions(+), 51 deletions(-)
>>
>> Signed-off-by: Yi Yang <yang.y.yi@gmail.com>
>>
>> --- a/kernel/capability.c.orig	2006-03-22 23:04:30.000000000 +0800
>> +++ b/kernel/capability.c	2006-03-22 23:07:06.000000000 +0800
>> @@ -5,7 +5,7 @@
>>   *
>>   * Integrated into 2.1.97+,  Andrew G. Morgan <morgan@transmeta.com>
>>   * 30 May 2002:	Cleanup, Robert M. Love <rml@tech9.net>
>> - */ 
>> + */
>>  
>>  #include <linux/capability.h>
>>  #include <linux/mm.h>
>> @@ -54,18 +54,18 @@ asmlinkage long sys_capget(cap_user_head
>>  
>>       if (version != _LINUX_CAPABILITY_VERSION) {
>>  	     if (put_user(_LINUX_CAPABILITY_VERSION, &header->version))
>> -		     return -EFAULT; 
>> +		     return -EFAULT;
>>     
> I think, it wants Lindent or something, not only delete tail whispaces, but also
> space indentation.
>
>   
Yes, there are too many such issues in kernel source tree, I don't know 
whether Linus uses
Lindent to reformat all the source code before release?
> regards,
> - --
> Jiri Slaby         www.fi.muni.cz/~xslaby
> ~\-/~      jirislaby@gmail.com      ~\-/~
> B67499670407CE62ACC8 22A032CC55C339D47A7E
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFEIZkXMsxVwznUen4RAgXfAKCUZKR72rZajvm4FExJt/WsXJKYMwCglKH1
> sUu3C59ZI/r27ZmsZlFfAvM=
> =rGzw
> -----END PGP SIGNATURE-----
>
>   


      reply	other threads:[~2006-03-23  1:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 15:36 [2.6.16 PATCH] some tail whitespace clean under subdirectory kernel Yi Yang
2006-03-22 18:36 ` Jiri Slaby
2006-03-23  1:05   ` Yi Yang [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=4421F471.3030505@gmail.com \
    --to=yang.y.yi@gmail.com \
    --cc=akpm@osdl.org \
    --cc=jirislaby@gmail.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