From: Dave Hansen <haveblue@us.ibm.com>
To: Adam Litke <agl@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Cleanup line-wrapping in pgtable.h
Date: Wed, 17 Aug 2005 11:19:13 -0700 [thread overview]
Message-ID: <1124302753.5879.11.camel@localhost> (raw)
In-Reply-To: <1124300739.3139.16.camel@localhost.localdomain>
On Wed, 2005-08-17 at 12:45 -0500, Adam Litke wrote:
> The line-wrapping in most of the include/asm/pgtable.h pte test/set
> macros looks horrible in my 80 column terminal. The following "test the
> waters" patch is how I would like to see them laid out. I realize that
> the braces don't adhere to CodingStyle but the advantage is (when taking
> wrapping into account) that the code takes up no additional space. How
> do people feel about making this change? Any better suggestions? I
> personally wouldn't like a lone closing brace like normal functions
> because of the extra lines eaten. I volunteer to patch up the other
> architectures if we reach a consensus.
I'd probably just leave it alone. Those are things that are virtually
never touched, and are quite unlikely to have any bugs in them.
But, if you do decide to change them, it might also be a nice idea to
consolidate some of the ones that are duplicated across architectures.
They could probably even go into the existing
include/asm-generic/pgtable.h. Please use full, proper CodingStyle if
you do decide to split them across several lines.
-- Dave
next prev parent reply other threads:[~2005-08-17 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 17:45 [RFC] Cleanup line-wrapping in pgtable.h Adam Litke
2005-08-17 17:56 ` Christoph Hellwig
2005-08-17 19:48 ` Alexey Dobriyan
2005-08-17 18:00 ` Tommy Reynolds
2005-08-17 18:19 ` Dave Hansen [this message]
2005-08-22 9:29 ` Pavel Machek
2005-08-22 21:11 ` Matthew Helsley
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=1124302753.5879.11.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=agl@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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