public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: i386 very early memory detection cleanup patch breaks the build
Date: Sat, 13 Mar 2004 13:43:45 -0800	[thread overview]
Message-ID: <40538091.9050707@zytor.com> (raw)
In-Reply-To: <1079198139.2512.19.camel@mulgrave>

James Bottomley wrote:
> The attached should fix it again.

Could you perhaps describe which architecture this is a problem on, and 
what its entry condition looks like?

> This tampering with the trampoline was extraneous to the actual patch. 
> The rule should be that if you don't understand what something is doing,
> don't try to fix it.

I removed it because I removed the VISWS dependency, thus making it 
redundant.  What you seem to be saying is that the dependency should 
have been on SMP not X86_SMP; if that's the issue then please make it so.

I think you just needed to apply your own rule to the above statement.

> In this case CONFIG_X86_TRAMPOLINE is needed for the subarch's that
> provide their own SMP code but still use the standard trampoline.  I
> always thought the visws used the trampoline even in UP boot, but if it
> doesn't, just take out the X86_VISWS dependency.

It doesn't anymore.  The only reason it did was because of stupid 
partitioning between head.S and trampoline.S, which the patch cleans up.

	-hpa

  parent reply	other threads:[~2004-03-13 21:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-13 17:15 i386 very early memory detection cleanup patch breaks the build James Bottomley
2004-03-13 19:48 ` James Bottomley
2004-03-13 21:43 ` H. Peter Anvin [this message]
2004-03-13 22:10   ` James Bottomley
2004-03-13 22:29     ` H. Peter Anvin
2004-03-13 22:38       ` James Bottomley
2004-03-14  2:05       ` James Bottomley
2004-03-14  2:16         ` 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=40538091.9050707@zytor.com \
    --to=hpa@zytor.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.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