public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64: some whitespace cleanups in paging code
Date: Wed, 5 Dec 2007 15:51:37 +0100	[thread overview]
Message-ID: <20071205145137.GA26700@elte.hu> (raw)
In-Reply-To: <1196865612128-git-send-email-joerg.roedel@amd.com>


* Joerg Roedel <joerg.roedel@amd.com> wrote:

> This patch does some whitespace cleanups in the paging code to fix 
> some checkpatch.pl warnings of my formerly merged cleanup patches.

thanks, applied.

btw., if there's any file you are particularly interested in cleaning up 
as a whole, you can use the --file option:

  scripts/checkpatch.pl --file include/asm-x86/pgtable_64.h

there's no hard policy on whether cleanups should be done 
pre-unification or post-unification. I've been using the following 
pretty sensible 3-step path when doing manual unifications:

- clean up the _32 and _64 file first (this is also easy to check - the 
  resulting .o or vmlinux must not differ with/without the patch)

- remove artificial differences (in a separate patch)

- do the unification (in a third patch)

the general rule, more patches are better than fewer patches. Most of 
our testing/bisetion infrastructure is per-patch/per-commit, so if some 
mistake happens (and mistakes happen all the time), the finer grained 
approach is always easier to sort out.

	Ingo

  reply	other threads:[~2007-12-05 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02 13:21 [PATCH 0/3] x86_64: some minor paging cleanups Joerg Roedel
2007-12-02 13:21 ` [PATCH 1/3] x86_64: define all _PAGE_* in terms of _PAGE_BIT_* Joerg Roedel
2007-12-04 12:36   ` Ingo Molnar
2007-12-04 12:38   ` Ingo Molnar
2007-12-04 15:06     ` Joerg Roedel
2007-12-04 21:07       ` Ingo Molnar
2007-12-05 10:52         ` Joerg Roedel
2007-12-05 11:27           ` Ingo Molnar
2007-12-05 11:42             ` Joerg Roedel
2007-12-05 12:30               ` Ingo Molnar
2007-12-05 14:40                 ` [PATCH] x86_64: some whitespace cleanups in paging code Joerg Roedel
2007-12-05 14:51                   ` Ingo Molnar [this message]
2007-12-05 16:37                   ` Heiko Carstens
2007-12-05 17:24                     ` Joerg Roedel
2007-12-02 13:21 ` [PATCH 2/3] x86_64: use __PAGE_KERNEL* instead of _KERNPG_TABLE for 2MB PTEs in memory initialization Joerg Roedel
2007-12-02 13:21 ` [PATCH 3/3] x86_64: use __PAGE_KERNEL_EXEC in ioremap_64.c Joerg Roedel

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=20071205145137.GA26700@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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