From: Oleg Nesterov <oleg@redhat.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Vishnu Pratap Singh <vishnu.ps@samsung.com>,
akpm@linux-foundation.org, richard@nod.at,
paulmck@linux.vnet.ibm.com, fabf@skynet.be,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
cpgs@samsung.com, pintu.k@samsung.com, vishu13285@gmail.com
Subject: Re: [PATCH] kernel/signal.c: whitespace fixes
Date: Tue, 2 Sep 2014 15:04:30 +0200 [thread overview]
Message-ID: <20140902130430.GA20751@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1409021445580.2481@pobox.suse.cz>
On 09/02, Jiri Kosina wrote:
>
> On Tue, 2 Sep 2014, Vishnu Pratap Singh wrote:
>
> > From: "vishnu.ps" <vishnu.ps@samsung.com>
> >
> > Fix minor errors and warning messages in kernel/signal.c. These errors were
> > reported by checkpatch while working with some modifications in signal.c
> > file.
> >
> > ERROR: code indent should use tabs where possible - 18
> > ERROR: need consistent spacing around '&' (ctx:WxO) - 11
> > ERROR: space prohibited after that '~' (ctx:OxW) - 11
> > ERROR: trailing whitespace - 4
> > ERROR: space required after that ',' (ctx:VxV) - 4
> > ERROR: trailing statements should be on next line - 3
> > ERROR: "foo * bar" should be "foo *bar" - 1
> >
> > total 52 errors fixed.
>
> I am not taking this through trivial.git; it just clutters results of 'git
> blame' horribly for no measurable gain.
>
> Changes like this are reasonable only if you make any real changes to the
> code at the same time.
I agree very much.
Vishnu, please think about those (me in particular ;) who need to backport
the fixes from time to time. Just suppose we have a bug in, say,
do_notify_parent_cldstop(), and it is fixed later. Now I will likely need
to backport your change too, and this is not trivial in general, plus this
adds the additional risk.
Oleg.
next prev parent reply other threads:[~2014-09-02 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 12:40 [PATCH] kernel/signal.c: whitespace fixes Vishnu Pratap Singh
2014-09-02 12:47 ` Jiri Kosina
2014-09-02 13:04 ` Oleg Nesterov [this message]
2014-09-02 12:48 ` Richard Weinberger
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=20140902130430.GA20751@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cpgs@samsung.com \
--cc=fabf@skynet.be \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pintu.k@samsung.com \
--cc=richard@nod.at \
--cc=viro@zeniv.linux.org.uk \
--cc=vishnu.ps@samsung.com \
--cc=vishu13285@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.