public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Adrian Bunk <bunk@kernel.org>,
	Alexey Starikovskiy <astarikovskiy@suse.de>,
	tglx@linutronix.de, James.Bottomley@HansenPartnership.com,
	linux-kernel@vger.kernel.org
Subject: Re: Voyager phys_cpu_present_map compile error
Date: Mon, 21 Apr 2008 09:00:06 -0400	[thread overview]
Message-ID: <480C8FD6.3030700@zytor.com> (raw)
In-Reply-To: <20080421120054.GA6788@elte.hu>

Ingo Molnar wrote:
> * Adrian Bunk <bunk@kernel.org> wrote:
> 
>> I shouldn't send bug reports at 3 in the morning...
>>
>> Attached is the .config for both Voyager build errors I reported.
> 
> thanks, the three patches below should fix it.
> 
> i ended up excluding Voyager configs from our test space some time ago 
> (and VISWS as well - there's one more visws fix in x86.git), that's how 
> this broke. These subarchitectures seem not to be used at all and the 
> code wont boot on normal PCs. We could mark it BROKEN but the fix seems 
> simple in any case.
> 

I talked to jejb about this, and pretty much the consensus was that if 
it breaks, mark it BROKEN, and let him come back and catch up.  Under 
those conditions, I'm willing to keep it in the tree.

VISWS is another matter.  It's entirely possible I have the only 
remaining VISWS in my garage; we have at least not been able to locate 
another.  Not that we have tried all that hard.

If there are no VISWS' left, we should just unload the code.

	-hpa

  parent reply	other threads:[~2008-04-21 13:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21  0:02 Voyager phys_cpu_present_map compile error Adrian Bunk
2008-04-21  8:53 ` Adrian Bunk
2008-04-21 12:00   ` Ingo Molnar
2008-04-21 12:55     ` H. Peter Anvin
2008-04-21 14:10       ` Status of SGI 320/540 (Visual Workstation) support? Adrian Bunk
2008-04-22  6:19         ` Andrey Panin
2008-04-22 13:29       ` Voyager phys_cpu_present_map compile error Andrew Morton
2008-04-22 15:25         ` Andy Whitcroft
2008-04-21 13:00     ` H. Peter Anvin [this message]
2008-04-21 15:42       ` James Bottomley
2008-04-21 20:03         ` Ingo Molnar
2008-04-21 23:08           ` James Bottomley
2008-04-21 19:55       ` Ingo Molnar
2008-04-21 20:03         ` H. Peter Anvin
2008-04-21 20:11           ` Ingo Molnar
2008-04-21 20:10             ` H. Peter Anvin
2008-04-23  8:53             ` Pavel Machek
2008-04-21 13:27     ` Adrian Bunk
2008-04-21 20:14       ` Ingo Molnar
2008-04-21 21:57         ` James Bottomley
2008-04-25 14:50         ` James Bottomley
2008-04-25 16:17           ` Adrian Bunk
2008-04-25 16:33             ` James Bottomley
2008-04-28 17:59               ` Ingo Molnar
2008-04-28 19:09                 ` James Bottomley
2008-04-21 15:58     ` James Bottomley
2008-04-21 19:51       ` Ingo Molnar
2008-04-21 20:09         ` Adrian Bunk
2008-04-21 20:13           ` Ingo Molnar
2008-04-21 20:26             ` Adrian Bunk
2008-04-21 20:29               ` Ingo Molnar
2008-04-21 21:02                 ` Adrian Bunk
2008-04-21 22:31                   ` Ingo Molnar
2008-04-26  7:43                     ` Pavel Machek
2008-04-27  0:44                       ` H. Peter Anvin
2008-04-27  1:06                         ` Adrian Bunk
2008-04-27  1:45                           ` 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=480C8FD6.3030700@zytor.com \
    --to=hpa@zytor.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=astarikovskiy@suse.de \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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