mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Paul Jackson <pj@sgi.com>
Cc: paulus@samba.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Linux-2.6.13-rc7
Date: Wed, 24 Aug 2005 20:15:44 +0100	[thread overview]
Message-ID: <20050824191544.GM9322@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050824114351.4e9b49bb.pj@sgi.com>

On Wed, Aug 24, 2005 at 11:43:51AM -0700, Paul Jackson wrote:
> Al Viro wrote:
> > ... breaks ppc64 since there we have node_to_cpumask() done as inlined
> > function, not a macro.  So we get __first_cpu(&node_to_cpumask(...),...),
> > with obvious consequences.
> 
> I sent a patch for this a few hours ago, thanks to Paul Mackerras's report:
> 
>   [PATCH 2.6.13-rc6] cpu_exclusive sched domains build fix
> 
> It just makes a local copy of the cpumask_t in a local variable on the stack.
> 
> I'm still a couple of hours from actually verifying that ppc64 builds with
> this - due to unrelated confusions on my end.  Perhaps you or Mackerras will
> report in first, to verify if this patch works as advertised.

It does, no (build) regressions.  BTW, tree is not far from allmodconfig
buildable on a bunch of targets now - yesterday pile of fixes was about
half of the set needed for that.  Most of the remaining stuff is for
m68k (and applies both to Linus' tree and m68k CVS); I'll send that today
and if Geert ACKs them, we will be _very_ close to having 2.6.13 build
out of the box on the following set:
alpha, amd64, arm (RPC and versatile being tracked), i386, ia64, m32r,
m68k (!SUN3), ppc (6xx, 44x, chestnut being tracked), ppc64, sparc,
sparc64, s390, s390x, uml-i386, uml-amd64.

All of these - with allmodconfig, alpha, amd64 and i386 being tracked
separately as SMP and UP.  Missing targets:
	frv: need newer toolchain on build box
	mips, parisc: need out-of-tree patches
	v850, m68knommu: gcc gives ICE on attempt to build cross-toolchain
	h8300: binutils in FC4 doesn't know what to do with that target,
have not tried that on sarge yet.
	sh, sh64: need kernel headers that would make glibc happy enough
to build libc headers for that puppy; I don't have them
	cris, xtensa: haven't looked into those
	arm26: needs gcc3 since gcc4 had dropped that target; I might take
a look into that on a sarge-based build box someday.

sun3 is seriously broken and I doubt that we'll see any takers for testing
2.6 on those anyway ;-)

A bunch of arm and ppc subarchitectures are not covered yet - I can add those
to build setup, just give me a list in order of preference.  Or ask me how
to set up a cross-build farm of your own...

  reply	other threads:[~2005-08-24 19:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24  5:08 Linux-2.6.13-rc7 Linus Torvalds
2005-08-24  6:43 ` Linux-2.6.13-rc7 Al Viro
2005-08-24 11:24   ` Linux-2.6.13-rc7 Dinakar Guniguntala
2005-08-24 18:43   ` Linux-2.6.13-rc7 Paul Jackson
2005-08-24 19:15     ` Al Viro [this message]
2005-08-24 20:13       ` Linux-2.6.13-rc7 Alexey Dobriyan
2005-08-24 20:34         ` Linux-2.6.13-rc7 Alexey Dobriyan
2005-08-24 21:38         ` Linux-2.6.13-rc7 Al Viro
2005-08-25  7:27           ` Linux-2.6.13-rc7 Alexey Dobriyan
2005-08-25 19:07             ` Linux-2.6.13-rc7 Al Viro
2005-08-25 22:16               ` Linux-2.6.13-rc7 Richard Henderson
2005-08-25 22:51                 ` Linux-2.6.13-rc7 Al Viro
2005-08-27  3:58                 ` Linux-2.6.13-rc7 Mitchell Blank Jr
2005-08-25  9:29       ` Linux-2.6.13-rc7 Geert Uytterhoeven
2005-08-25 13:59         ` Linux-2.6.13-rc7 Sam Creasey
2005-08-25 14:12           ` Linux-2.6.13-rc7 Al Viro
2005-08-25 14:16             ` Linux-2.6.13-rc7 Geert Uytterhoeven
2005-08-25 14:17             ` Linux-2.6.13-rc7 Sam Creasey
2005-08-24 22:40 ` Linux-2.6.13-rc7 : OK Willy TARREAU
2005-08-25 14:04 ` Linux-2.6.13-rc7 Erik Mouw
2005-08-27  4:33   ` Linux-2.6.13-rc7 Deepak Saxena
2005-08-29 13:33     ` Linux-2.6.13-rc7 Erik Mouw
2005-08-25 17:49 ` Linux-2.6.13-rc7 Sebastian Kaergel
2005-08-25 16:23   ` Linux-2.6.13-rc7 Antonino A. Daplas
2005-08-25 19:01     ` Linux-2.6.13-rc7 Sebastian Kaergel
2005-08-25 17:45       ` Linux-2.6.13-rc7 Antonino A. Daplas
2005-08-25 18:47       ` Linux-2.6.13-rc7 Sylvain Meyer
2005-08-25 23:25         ` Linux-2.6.13-rc7 Antonino A. Daplas
2005-08-26 10:45 ` Linux-2.6.13-rc7 Danny ter Haar
2005-08-26 13:51   ` Linux-2.6.13-rc7 Danny ter Haar
2005-08-27 11:37     ` Linux-2.6.13-rc7 Danny ter Haar
2005-08-27 11:57       ` Linux-2.6.13-rc7 Danny ter Haar
2005-08-27  3:45 ` Linux-2.6.13-rc7 Masoud Sharbiani
2005-08-25  0:20 Linux-2.6.13-rc7 Voluspa

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=20050824191544.GM9322@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=pj@sgi.com \
    --cc=torvalds@osdl.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®