mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Chinner <dgc@sgi.com>
Cc: linux-next@vger.kernel.org, xfs-masters@oss.sgi.com,
	Christoph Hellwig <hch@infradead.org>,
	Lachlan McIlroy <lachlan@sgi.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: xfs build failure
Date: Wed, 30 Apr 2008 16:42:18 +1000	[thread overview]
Message-ID: <20080430164218.9c2bfb1c.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080430063544.GA108924158@sgi.com>

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

Hi David,

On Wed, 30 Apr 2008 16:35:44 +1000 David Chinner <dgc@sgi.com> wrote:
>
> Ah, I see the problem - a CONFIG_XFS_DEBUG build includes linux/random.h
> in a debug header file. That's probably why I didn't catch it (I need to
> check the .config on my build test tree).
> 
> I'll get it fixed properly, but in the mean time the include you've got
> there will suffice...

Could you make sure something gets sent to Linus pretty quickly as this
breaks a lot of the powerpc builds at the moment (see
http://kisskb.ellerman.id.au/kisskb/branch/3/).  Or should I do my patch
up and sent it?

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-30  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  4:00 Stephen Rothwell
2008-04-30  6:35 ` David Chinner
2008-04-30  6:42   ` Stephen Rothwell [this message]
2008-04-30  7:11     ` [PATCH, XFS] Fix random.h include for non-debug builds David Chinner

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=20080430164218.9c2bfb1c.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=dgc@sgi.com \
    --cc=hch@infradead.org \
    --cc=lachlan@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xfs-masters@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®