linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Bug report: CELL on linux-2.6.19-git7 won't build,
Date: Thu, 07 Dec 2006 14:34:10 +0000	[thread overview]
Message-ID: <1165502050.5253.348.camel@pmac.infradead.org> (raw)
In-Reply-To: <20061206200143.GE17931@austin.ibm.com>

On Wed, 2006-12-06 at 14:01 -0600, Linas Vepstas wrote:
> > Yes, that's with CONFIG_HEADERS_CHECK=y.  
> 
> I have to turn that off. Its annoying, actually.

That means it's doing its job :)

The fact that this bug made it all the way into Linus' tree without
getting noticed means that too few people are using it, though.

-- 
dwmw2

      reply	other threads:[~2006-12-07 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 19:27 Bug report: CELL on linux-2.6.19-git7 won't build, Linas Vepstas
2006-12-06 19:45 ` Geoff Levand
2006-12-06 20:01   ` Linas Vepstas
2006-12-07 14:34     ` David Woodhouse [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=1165502050.5253.348.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=arnd@arndb.de \
    --cc=linas@austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).