From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] powerpc/mm: Fix memory_block_size_bytes() for non-pseries
Date: Sun, 03 Jul 2011 00:15:01 +1000 [thread overview]
Message-ID: <1309616101.14501.262.camel@pasglop> (raw)
In-Reply-To: <20110702102333.GC17482@elte.hu>
On Sat, 2011-07-02 at 12:23 +0200, Ingo Molnar wrote:
> It's certainly not a hard rule - but note that the file in question
> (arch/powerpc/platforms/pseries/hotplug-memory.c) has a rather
> inconsistent comment style, sometimes even within the same function:
>
> /*
> * Remove htab bolted mappings for this section of memory
> */
> ...
>
> /* Ensure all vmalloc mappings are flushed in case they also
> * hit that section of memory
> */
>
> That kind of inconsistency within the same .c file and within the
> same function is not defensible with a "style is a matter of taste"
> argument.
Right, that's a matter of different people with different taste mucking
around with the same file I suppose.
Most of this probably predates my involvement as a maintainer but even
if not (and I really can't be bothered digging into the history), it
might very well be something I didn't pay attention to while reviewing.
Seriously, it's so low on the scale of what matters ... I'm sure we both
have more valuable stuff to spend our time and energy on :-)
Cheers,
Ben.
prev parent reply other threads:[~2011-07-02 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 0:57 [PATCH 2/2] powerpc/mm: Fix memory_block_size_bytes() for non-pseries Benjamin Herrenschmidt
2011-07-01 12:15 ` Ingo Molnar
2011-07-01 23:15 ` Benjamin Herrenschmidt
2011-07-02 10:23 ` Ingo Molnar
2011-07-02 14:15 ` Benjamin Herrenschmidt [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=1309616101.14501.262.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).