From: John Weber <john.weber@linux.org>
To: linux-kernel@vger.kernel.org
Subject: Re: janitorial PATCH: 2.4: nvram.c Lindent
Date: Tue, 30 Jul 2002 22:45:28 -0400 [thread overview]
Message-ID: <3D474F48.1030109@linux.org> (raw)
In-Reply-To: ai75c5$1ft$1@penguin.transmeta.com
> If you're doing these kinds of Lindent changes, you might as well also
> fix another non-linuxism:
>
> return (x); -> return x;
>
> I don't know why some people seem to think that "return" is a function
> with an argument..
Excuse me? Anyone care to explain?
> I guess that one isn't mentioned in the CodingStyles thing. I'm lazy.
> Bad Bad Linus.
next prev parent reply other threads:[~2002-07-31 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 22:45 janitorial PATCH: 2.4: nvram.c Lindent Tim Hockin
2002-07-30 22:52 ` Linus Torvalds
2002-07-31 2:45 ` John Weber [this message]
[not found] ` <200207302252.g6UMqrj01538@penguin.transmeta.com>
2002-07-31 5:29 ` Tim Hockin
2002-08-01 10:51 ` Pavel Machek
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=3D474F48.1030109@linux.org \
--to=john.weber@linux.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 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.