mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Gustavo F. Padovan" <gustavo@las.ic.unicamp.br>
Cc: linux-kernel@vger.kernel.org, the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH 5/6] x86: coding style fixes to arch/x86/kernel/traps_64.c
Date: Thu, 31 Jul 2008 18:31:50 +0200	[thread overview]
Message-ID: <20080731163150.GD26393@elte.hu> (raw)
In-Reply-To: <1217310536-7181-6-git-send-email-gustavo@las.ic.unicamp.br>


* Gustavo F. Padovan <gustavo@las.ic.unicamp.br> wrote:

>  void printk_address(unsigned long address, int reliable)
>  {
> -	printk(" [<%016lx>] %s%pS\n", address, reliable ? "": "? ", (void *) address);
> +	printk(" [<%016lx>] %s%pS\n", address, reliable ?
> +			"" : "? ", (void *) address);

careful with line 80 warnings. This one is better broken up the 
following way:

	printk(" [<%016lx>] %s%pS\n",
	       address, reliable ? "": "? ", (void *) address);

so that logically coherent pieces of code stay together. (the arguments 
to the printk() function call in this case)

>  #if DEBUG_STKSZ > EXCEPTION_STKSZ
> -		[N_EXCEPTION_STACKS ... N_EXCEPTION_STACKS + DEBUG_STKSZ / EXCEPTION_STKSZ - 2] = "#DB[?]"
> +		[N_EXCEPTION_STACKS ... N_EXCEPTION_STACKS + DEBUG_STKSZ /
> +			EXCEPTION_STKSZ - 2] = "#DB[?]"

this too is done better in another way:

	[N_EXCEPTION_STACKS ... 
	 N_EXCEPTION_STACKS + DEBUG_STKSZ / EXCEPTION_STKSZ - 2] = "#DB[?]"

> -	// debugging aid: "show_stack(NULL, NULL);" prints the
> -	// back trace for this cpu.
> +	/* debugging aid: "show_stack(NULL, NULL);" prints the
> +	  back trace for this cpu. */

please use the standard multi-line comment format:

	/*
	 * Multi-line ...........
	 * .............. comment.
	 */

i've applied your patches already to x86/cleanups, so please send a 
delta patch against that branch to fix these few items up. You can pick 
it up via:

    http://people.redhat.com/mingo/tip.git/README

and do:

    git-checkout tip/x86/cleanups

to check out that exact tree. (You might also want to work against 
tip/master, which has the same changes.)

	Ingo

  parent reply	other threads:[~2008-07-31 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  5:48 [PATCH 0/6] x86: coding style fixes to arch/x86/kernel/ Gustavo F. Padovan
2008-07-29  5:48 ` [PATCH 1/6] x86: coding styles fixes to arch/x86/kernel/process_64.c Gustavo F. Padovan
2008-07-29  5:48   ` [PATCH 2/6] x86: add KERN_INFO to printks on process_64.c Gustavo F. Padovan
2008-07-29  5:48     ` [PATCH 3/6] x86: coding style fixes to arch/x86/kernel/crash_dump_64.c Gustavo F. Padovan
2008-07-29  5:48       ` [PATCH 4/6] x86: coding style fixes to arch/x86/kernel/signal_64.c Gustavo F. Padovan
2008-07-29  5:48         ` [PATCH 5/6] x86: coding style fixes to arch/x86/kernel/traps_64.c Gustavo F. Padovan
2008-07-29  5:48           ` [PATCH 6/6] x86: coding style fixes to arch/x86/kernel/sys_x86_64.c Gustavo F. Padovan
2008-07-31 16:31           ` Ingo Molnar [this message]
2008-07-31 16:21 ` [PATCH 0/6] x86: coding style fixes to arch/x86/kernel/ Ingo Molnar

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=20080731163150.GD26393@elte.hu \
    --to=mingo@elte.hu \
    --cc=gustavo@las.ic.unicamp.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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

all inboxes | Powered by JetHome®