From: Ingo Molnar <mingo@elte.hu>
To: James Morris <jmorris@namei.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] ipc/msg.c: clean up coding style
Date: Fri, 28 Jul 2006 10:53:15 +0200 [thread overview]
Message-ID: <20060728085315.GA14622@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0607280153490.13981@d.namei>
* James Morris <jmorris@namei.org> wrote:
> On Thu, 27 Jul 2006, Ingo Molnar wrote:
>
> > > Let's not go BSD way.
> >
> > again, lets not have overlong line 80 prototypes.
>
> I thought Linus gave his blessing for long lines for prototypes (up to
> 120 chars?), to make it easier to grep the code for function
> prototypes.
i think that's a tool issue. If you need multiline grep, use the 'mg'
perl-script from:
http://freshmeat.net/projects/mg_multi_line_grep/
for example, to see all syscall prototypes in kernel/*.c:
mg -e "asmlinkage.*\n*.*sys.*\n*.*{" kernel/*.c
Ingo
prev parent reply other threads:[~2006-07-28 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 13:53 [patch] ipc/msg.c: clean up coding style Ingo Molnar
2006-07-27 14:46 ` Alexey Dobriyan
2006-07-27 16:24 ` Ingo Molnar
2006-07-27 16:45 ` Daniel Walker
2006-07-28 5:56 ` James Morris
2006-07-28 8:53 ` Ingo Molnar [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=20060728085315.GA14622@elte.hu \
--to=mingo@elte.hu \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=jmorris@namei.org \
--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