public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
	Yinghai Lu <yhlu.kernel@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: about relocs.c on x86
Date: Thu, 31 Jan 2008 13:04:27 +0100	[thread overview]
Message-ID: <20080131120427.GA12571@elte.hu> (raw)
In-Reply-To: <20080131103842.GA550@uranus.ravnborg.org>


* Sam Ravnborg <sam@ravnborg.org> wrote:

> As for the Makefiles - I looked at them last time and only issue that 
> kept me away for unifying them was that I did not understand the 
> linking order requirments and I did not see enough benefit at that 
> time to invest the time to unify them. Each of the remaining Makefile 
> should be unifyable in less than 10 steps each. It is just work that 
> are waitng to be done.

the only real issue i remember in this area are hidden link dependencies 
in terms of ordering init sequences.

and there's just no other sane approach here but to do finegrained 
changes (so that any breakage remains bisectable) and take the plunge 
down that road. Any implicit link dependency is a bug in the waiting 
anyway, which we want to fix. So feel free to unify this area, whenver 
you find the time.

	Ingo

  parent reply	other threads:[~2008-01-31 12:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  8:07 about relocs.c on x86 Yinghai Lu
2008-01-31  8:33 ` Chris Snook
2008-01-31  9:13   ` Yinghai Lu
2008-01-31  9:17     ` Chris Snook
2008-01-31  9:52 ` Ingo Molnar
2008-01-31 10:02   ` Harvey Harrison
2008-01-31 10:11     ` Ingo Molnar
2008-01-31 10:21       ` Harvey Harrison
2008-01-31 10:38       ` Sam Ravnborg
2008-01-31 10:44         ` Harvey Harrison
2008-01-31 12:04         ` Ingo Molnar [this message]
2008-01-31 17:47       ` H. Peter Anvin

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=20080131120427.GA12571@elte.hu \
    --to=mingo@elte.hu \
    --cc=harvey.harrison@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.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