From: Al Viro <viro@ZenIV.linux.org.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: fault.c cleanup, what else could it be
Date: Mon, 30 Mar 2009 00:48:39 +0100 [thread overview]
Message-ID: <20090329234839.GL28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20090329232422.GA9873@elte.hu>
On Mon, Mar 30, 2009 at 01:24:22AM +0200, Ingo Molnar wrote:
>
> * Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> > I have personally stopped sending anything against pure arch/x86/
> > if there is even a smallest chance it can be prettyfied like this.
>
> Before you volunteer reviewing x86 code for us (thanks for that!),
> may i direct your urgent attention at code in your own area of
> responsibility - such as fs/proc/base.c:
>
> total: 85 errors, 39 warnings, 2 checks, 3147 lines checked
>
> I filtered out the relevant ones for you below.
This is precisely what's wrong with your advocacy. I actually have no
problem with specific instances pointed to by checkpatch.pl in this case;
when code in question gets touched, sure, getting rid of those would be OK.
*HOWEVER*, implying that this noise should take priority over any real work
is bloody insane. And replying to mail that questions the usefulness of
such activity with "shut up, do what you've pretty much called pointless
and don't come back until you are done"... fie, sir.
next prev parent reply other threads:[~2009-03-29 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 17:56 fault.c cleanup, what else could it be Alexey Dobriyan
2009-03-29 20:39 ` David Miller
2009-03-29 23:24 ` Ingo Molnar
2009-03-29 23:48 ` Al Viro [this message]
2009-03-30 1:13 ` Ingo Molnar
2009-03-30 1:33 ` Al Viro
2009-03-30 1:49 ` Ingo Molnar
2009-03-30 4:25 ` Al Viro
2009-03-30 22:16 ` Alexey Dobriyan
2009-03-30 0:29 ` Alexey Dobriyan
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=20090329234839.GL28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.