mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Chinner <david@fromorbit.com>
Cc: geert@linux-m68k.org, lachlan@sgi.com,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	xfs@oss.sgi.com, linux-m68k@vger.kernel.org
Subject: Re: [GIT PULL] XFS update for 2.6.27-rc4
Date: Thu, 14 Aug 2008 16:03:27 -0700	[thread overview]
Message-ID: <20080814160327.bf2a2673.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080814225130.GB19760@disturbed>

On Fri, 15 Aug 2008 08:51:30 +1000
Dave Chinner <david@fromorbit.com> wrote:

> > |   CC      arch/m68k/kernel/asm-offsets.s
> > | In file included from linux/include/linux/mm_types.h:12,
> > |                  from linux/include/linux/sched.h:61,
> > |                  from linux/arch/m68k/kernel/asm-offsets.c:12:
> > | linux/include/linux/completion.h: In function 'try_wait_for_completion':
> > | linux/include/linux/completion.h:80: error: dereferencing pointer to incomplete type
> > | linux/include/linux/completion.h: In function 'completion_done':
> > | linux/include/linux/completion.h:99: error: dereferencing pointer to incomplete type
> > | make[3]: *** [arch/m68k/kernel/asm-offsets.s] Error 1
> > | make[2]: *** [prepare0] Error 2
> > | make[1]: *** [sub-make] Error 2
> > 
> > (cfr. http://kisskb.ellerman.id.au/kisskb/buildresult/42080/)
> > 
> > Apparently there was not sufficient time between entering linux-next and
> > Linus' tree to notice this breakage before, while the original patch was already
> > posted on July 11...
> 
> It spent the time between then and now in the -mm tree. Seems
> like nobody is building m68k out of -mm.

I test m68k build regularly, but only allmodconfig.

Our (complexity(config system) * complexity(header files)) is so large
that compilation testing doesn't prove anything useful.  You just have
to check your homework very carefully and don earplugs for the
inevitable explosions.

> I'm out for the next 3 days, but it seems to me that the easiest fix
> is to move that code out of the header (i.e. uninline them) so the
> patch below is only compile tested on x86_64 - I've got to go load a
> trailer and get moving...

I'll give it a whizz on a few architectures, but it looks quite safe
from here.  It looks like the uninlining was desirable from a
size/speed POV anyway.



      reply	other threads:[~2008-08-14 23:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  8:11 Lachlan McIlroy
2008-08-13  8:16 ` Andrew Morton
2008-08-13  8:29   ` Lachlan McIlroy
2008-08-13  8:50   ` Dave Chinner
2008-08-14 15:45 ` Geert Uytterhoeven
2008-08-14 22:51   ` Dave Chinner
2008-08-14 23:03     ` Andrew Morton [this message]

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=20080814160327.bf2a2673.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=geert@linux-m68k.org \
    --cc=lachlan@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xfs@oss.sgi.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

all inboxes | Powered by JetHome®