LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: dsterba@suse.cz, Christoph Hellwig <hch@infradead.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: use #pragma once
Date: Thu, 26 Apr 2018 22:24:44 +0300 [thread overview]
Message-ID: <20180426192444.GA4919@avx2> (raw)
In-Reply-To: <20180426102629.scwtdeijbo3342gp@twin.jikos.cz>
On Thu, Apr 26, 2018 at 12:26:29PM +0200, David Sterba wrote:
> On Wed, Apr 25, 2018 at 11:55:31PM +0300, Alexey Dobriyan wrote:
> > On Tue, Apr 24, 2018 at 06:54:09AM -0700, Christoph Hellwig wrote:
> > > On Tue, Apr 24, 2018 at 12:35:34AM +0300, Alexey Dobriyan wrote:
> > > > Bring /proc into 21st century.
> > >
> > > Please explain what this actually buys us except for being pointlessly
> > > different from the rest of the kernel?
> >
> > Negative LOC diff, less junk in preprocessor hashtables.
>
> There are about 20k header files, none of them has #pragma once.
> Updating that will bring many unnesessry git commits.
If you don't obey sometimes silly rule re splitting patches,
it can be done in much less.
> I doubt that one more define in preprocessor tables is a problem we
> should fix.
Those eat cycles and memory one define at a time.
> The LOC argument also does not sound very convincing.
When was the last time you did -80 kLOC patch for free?
> The include protection is at the top of the file, not mixed among other
> code. Replacing 2-3 lines with one will be barely noticeable.
next prev parent reply other threads:[~2018-04-26 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 21:35 Alexey Dobriyan
2018-04-24 13:54 ` Christoph Hellwig
2018-04-25 20:55 ` Alexey Dobriyan
2018-04-26 10:26 ` David Sterba
2018-04-26 10:33 ` Christoph Hellwig
2018-04-26 19:25 ` Alexey Dobriyan
2018-04-26 19:24 ` Alexey Dobriyan [this message]
2018-05-01 22:13 ` Andrew Morton
2018-05-03 22:14 ` Rasmus Villemoes
2018-05-03 22:42 ` Al Viro
2018-05-03 23:23 ` Rasmus Villemoes
2018-05-04 2:58 ` Al Viro
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=20180426192444.GA4919@avx2 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dsterba@suse.cz \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH] proc: use #pragma once' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).