mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Ingo Molnar <mingo@elte.hu>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip V2] x86: cpu architecture debug code
Date: Tue, 10 Mar 2009 15:53:28 -0400	[thread overview]
Message-ID: <36674.1236714808@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 10 Mar 2009 16:20:29 BST." <20090310152029.GN3850@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

On Tue, 10 Mar 2009 16:20:29 BST, Ingo Molnar said:

> If you look at arch/x86/mm/fault.c, they are sorted by length, 
> and within the same length they are sorted alphabetically.

Huh? I just did a 'git pull' of Linus's tree, and I see fault.c looking like:

#include <linux/signal.h>
#include <linux/sched.h>
#include <linux/kernel.h>
#include <linux/errno.h>
#include <linux/string.h>
#include <linux/types.h>
#include <linux/ptrace.h>
#include <linux/mmiotrace.h>
#include <linux/mman.h>
#include <linux/mm.h>
#include <linux/smp.h>
#include <linux/interrupt.h>

Not sure how it's sorted, but it's appparently not by length first.  Also,
wouldn't logical interdependency count for something here, including stuff
in the order needed?


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2009-03-10 19:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 11:23 Jaswinder Singh Rajput
2009-03-10 12:28 ` Ingo Molnar
2009-03-10 15:09   ` Jaswinder Singh Rajput
2009-03-10 15:20     ` Ingo Molnar
2009-03-10 16:09       ` Jaswinder Singh Rajput
2009-03-10 17:45         ` Ingo Molnar
2009-03-10 23:55           ` Jaswinder Singh Rajput
2009-03-11 10:53             ` Ingo Molnar
2009-03-11 11:25               ` Jaswinder Singh Rajput
2009-03-11 11:34                 ` Ingo Molnar
2009-03-13  7:34                 ` Jeremy Fitzhardinge
2009-03-13  8:07                   ` Jaswinder Singh Rajput
2009-03-11 11:54           ` Jaswinder Singh Rajput
2009-03-11 12:45             ` Jaswinder Singh Rajput
2009-03-11 12:50               ` Ingo Molnar
2009-03-11 13:13                 ` Ingo Molnar
2009-03-11 13:43                   ` Jaswinder Singh Rajput
2009-03-11 13:48                     ` Ingo Molnar
2009-03-13  7:37                     ` Jeremy Fitzhardinge
2009-03-10 17:48         ` [tip:x86/debug] " Jaswinder Singh Rajput
2009-03-10 19:53       ` Valdis.Kletnieks [this message]
2009-03-10 22:00         ` [git-pull -tip V2] " 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=36674.1236714808@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=hpa@zytor.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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®