public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Cc: Adam Kropelin <akropel1@rochester.rr.com>
Subject: Re: [PATCH] - trivial comment fixups in init/main.c
Date: Tue, 17 Aug 2004 19:53:51 +1000	[thread overview]
Message-ID: <20040817095601.4E7F22BEC3@ozlabs.org> (raw)
In-Reply-To: Your message of "Tue, 13 Jul 2004 11:39:00 MST." <40F42C44.5010603@am.sony.com>

In message <40F42C44.5010603@am.sony.com> you write:
> This patch has some trivial comment fixups for init/main.c, to bring
> the comments into consistency with the coding style of the kernel.

Personally, I prefer my comments quiet and unobtrusive, and I think
you'll find Linus' code tends to be the same.

Not to start a flame war, but since I started using a colorizing
editor for code, I found there was no need to waste vertical space
with large banners.  (This in my mind justifies the X project's entire
existence).

Sorry,
Rusty.

> diff -u -X /home/tbird/dontdiff -ruN linux-2.6.7.orig/init/main.c patch5/init/main.c
> --- linux-2.6.7.orig/init/main.c	2004-06-15 22:19:01.000000000 -0700
> +++ patch5/init/main.c	2004-07-12 12:34:55.000000000 -0700
> @@ -238,8 +264,10 @@
>   __setup("debug", debug_kernel);
>   __setup("quiet", quiet_kernel);
> 
> -/* Unknown boot options get handed to init, unless they look like
> -   failed parameters */
> +/*
> + * Unknown boot options get handed to init, unless they look like
> + * failed parameters
> + */
>   static int __init unknown_bootoption(char *param, char *val)
>   {
>   	/* Change NUL term back to "=", to make "param" the whole string. */
> @@ -250,8 +278,10 @@
>   	if (obsolete_checksetup(param))
>   		return 0;
> 
> -	/* Preemptive maintenance for "why didn't my mispelled command
> -           line work?" */
> +	/*
> +	 * Preemptive maintenance for "why didn't my mispelled command
> +	 * line work?"
> +	 */
>   	if (strchr(param, '.') && (!val || strchr(param, '.') < val)) {
>   		printk(KERN_ERR "Unknown boot option `%s': ignoring\n", param);
>   		return 0;
> @@ -289,7 +319,8 @@
>   	unsigned int i;
> 
>   	execute_command = str;
> -	/* In case LILO is going to boot us with default command line,
> +	/*
> +	 * In case LILO is going to boot us with default command line,
>   	 * it prepends "auto" before the whole cmdline which makes
>   	 * the shell think it should execute a script with such name.
>   	 * So we ignore all arguments entered _before_ init=... [MJ]
> @@ -483,9 +514,9 @@
>   	check_bugs();
> 
>   	/*
> -	 *	We count on the initial thread going ok
> -	 *	Like idlers init is an unlocked kernel thread, which will
> -	 *	make syscalls (and thus be locked).
> +	 * We count on the initial thread going ok
> +	 * Like idlers init is an unlocked kernel thread, which will
> +	 * make syscalls (and thus be locked).
>   	 */
>   	init_idle(current, smp_processor_id());
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2004-08-17  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 18:39 [PATCH] - trivial comment fixups in init/main.c Tim Bird
2004-08-17  9:53 ` Rusty Russell [this message]
2004-08-17 11:45   ` Adam Kropelin
2004-08-17 17:31   ` Tim Bird
2004-08-17 17:42     ` Christoph Hellwig
2004-08-26  8:42       ` Rusty Russell

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=20040817095601.4E7F22BEC3@ozlabs.org \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.bird@am.sony.com \
    /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