From: Sachin Sant <sachinp@in.ibm.com>
To: linux-s390@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, heiko.carstens@de.ibm.com
Subject: Next March 27 : s390 defconfig build failure
Date: Fri, 27 Mar 2009 19:27:04 +0530 [thread overview]
Message-ID: <49CCDB30.7010203@in.ibm.com> (raw)
In-Reply-To: <20090327231924.4e4168c5.sfr@canb.auug.org.au>
Today's Next defconfig s390 build failed with
arch/s390/hypfs/hypfs_diag.c: In function diag204_free_buffer:
arch/s390/hypfs/hypfs_diag.c:364: error: implicit declaration of function free_pages
arch/s390/hypfs/hypfs_diag.c: In function diag204_alloc_rbuf:
arch/s390/hypfs/hypfs_diag.c:384: error: implicit declaration of function __get_free_pages
arch/s390/hypfs/hypfs_diag.c:384: error: GFP_KERNEL undeclared (first use in this function)
arch/s390/hypfs/hypfs_diag.c:384: error: (Each undeclared identifier is reported only once
arch/s390/hypfs/hypfs_diag.c:384: error: for each function it appears in.)
arch/s390/hypfs/hypfs_diag.c:384: warning: cast to pointer from integer of different size
arch/s390/hypfs/hypfs_diag.c: In function diag224_get_name_table:
arch/s390/hypfs/hypfs_diag.c:503: error: implicit declaration of function kmalloc
arch/s390/hypfs/hypfs_diag.c:503: error: GFP_KERNEL undeclared (first use in this function)
arch/s390/hypfs/hypfs_diag.c:503: error: GFP_DMA undeclared (first use in this function)
arch/s390/hypfs/hypfs_diag.c:503: warning: assignment makes pointer from integer without a cast
arch/s390/hypfs/hypfs_diag.c:507: error: implicit declaration of function kfree
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next parent reply other threads:[~2009-03-27 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090327231924.4e4168c5.sfr@canb.auug.org.au>
2009-03-27 13:57 ` Sachin Sant [this message]
2009-03-27 14:40 ` Next March 27 : s390 defconfig build failure Heiko Carstens
2009-03-30 9:51 ` Sachin Sant
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=49CCDB30.7010203@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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