All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Valentin Ilie <valentin.ilie@gmail.com>
Cc: richard -rw- weinberger <richard.weinberger@gmail.com>,
	akpm@linux-foundation.org, paul.gortmaker@windriver.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: sys.c: Fixed coding style issues
Date: Sat, 21 Apr 2012 15:35:58 -0700	[thread overview]
Message-ID: <4F93364E.2010805@xenotime.net> (raw)
In-Reply-To: <CAHuBVBZtCJ_o2DR9+z+BokS05JbCn2-zAh5sBnpwZo97-YaReA@mail.gmail.com>

On 04/21/2012 08:27 AM, Valentin Ilie wrote:

>> This kind of patch is not easy to review.
>> Can you please prove that no logic has changed?
>> E.g. By comparing the object file before and after your patch...
> 
> Everything seems to be OK.
> 
> The diff is because the old version had an unnecessary \n in two places.

But Richard asked you to compare the object files (binary files,
kernel/sys.o) to make sure that they are the same.


> $ checkpatch.pl -q --file --terse /tmp/test/sys.c | grep total
> total: 33 errors, 18 warnings, 2057 lines checked
> $ checkpatch.pl -q --file --terse /tmp/test/sys_patched.c | grep total
> total: 4 errors, 14 warnings, 2055 lines checked
> 
> $ diff -iEbwB sys.c sys_patched.c
> 215,216c215
> < 			else if ((who != cred->uid) &&
> < 				 !(user = find_user(who)))
> ---
>> 		else if ((who != cred->uid) && !(user = find_user(who)))
> 280,281c279
> < 			else if ((who != cred->uid) &&
> < 				 !(user = find_user(who)))
> ---
>> 		else if ((who != cred->uid) && !(user = find_user(who)))
> 
> 



-- 
~Randy

  reply	other threads:[~2012-04-21 22:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 11:42 [PATCH] kernel: sys.c: Fixed coding style issues Valentin Ilie
2012-04-21 12:34 ` richard -rw- weinberger
2012-04-21 15:27   ` Valentin Ilie
2012-04-21 22:35     ` Randy Dunlap [this message]
2012-04-21 22:36       ` Randy Dunlap
2012-04-22  0:43         ` Valentin Ilie
2012-04-24 13:17 ` Paul Gortmaker

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=4F93364E.2010805@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=richard.weinberger@gmail.com \
    --cc=valentin.ilie@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.