public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Theodore Tso <tytso@MIT•EDU>
Cc: linux-next@vger•kernel.org
Subject: linux-next: ext4 tree build failure
Date: Tue, 28 Apr 2009 11:27:22 +1000	[thread overview]
Message-ID: <20090428112722.22c844ea.sfr@canb.auug.org.au> (raw)

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

Hi Ted,

Today's linux-next build (powerpc ppc64_defconfig) failed like this:

fs/ext4/super.c: In function 'ext4_put_super':
fs/ext4/super.c:590: error: implicit declaration of function 'vfree'
fs/ext4/super.c: In function 'ext4_fill_flex_info':
fs/ext4/super.c:1644: error: implicit declaration of function 'vmalloc'
fs/ext4/super.c:1644: warning: assignment makes pointer from integer without a cast

Probably caused by commit a4ded943dff5de6fee2b397de9bcb2ffd5556253
("ext4: Fallback to vmalloc if kmalloc can't allocate s_flex_groups
array").  Presumably a missing explicit include of linux/vmalloc.h.

I have used the ext4 tree from next-20090424.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

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

             reply	other threads:[~2009-04-28  1:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  1:27 Stephen Rothwell [this message]
2009-04-28 11:23 ` linux-next: ext4 tree build failure Theodore Tso
2009-04-28 11:44   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-06-16  4:44 Stephen Rothwell
2009-06-16 20:30 ` Theodore Tso
2009-06-16 22:11   ` Theodore Tso
2009-06-17  5:46     ` Stephen Rothwell
2009-06-17  4:16   ` Pekka Enberg
2009-12-10  0:38 Stephen Rothwell
2009-12-10  2:10 ` tytso
2009-12-10  2:33   ` Stephen Rothwell

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=20090428112722.22c844ea.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tytso@MIT$(echo .)EDU \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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