From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUILD-FAILURE] linux-next: Tree for June 30
Date: Mon, 30 Jun 2008 23:51:00 +0530 [thread overview]
Message-ID: <4869240C.9060503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080630175925.GQ20826@kernel.dk>
Jens Axboe wrote:
> On Mon, Jun 30 2008, Kamalesh Babulal wrote:
>> Hi Stephen,
>>
>> next-20080630 kernel build fails x86 box
>>
>> fs/bio-integrity.c: In function `bio_integrity_add_page':
>> include/linux/bio.h:368: sorry, unimplemented: inlining failed in call to 'bvec_nr_vecs': function body not available
>> fs/bio-integrity.c:135: sorry, unimplemented: called from here
>> make[1]: *** [fs/bio-integrity.o] Error 1
>> make: *** [fs] Error 2
>
> Gah, I can't believe gcc errors on that. This should fix it, I'll
> integrate with the patchset.
Hi Jens,
Thanks, the patch fixes the build failure.
>
> diff --git a/fs/bio.c b/fs/bio.c
> index bc865b1..7761c84 100644
> --- a/fs/bio.c
> +++ b/fs/bio.c
> @@ -50,7 +50,7 @@ static struct biovec_slab bvec_slabs[BIOVEC_NR_POOLS] __read_mostly = {
> */
> struct bio_set *fs_bio_set;
>
> -inline unsigned int bvec_nr_vecs(unsigned short idx)
> +unsigned int bvec_nr_vecs(unsigned short idx)
> {
> return bvec_slabs[idx].nr_vecs;
> }
> diff --git a/include/linux/bio.h b/include/linux/bio.h
> index 62f0be9..0933a14 100644
> --- a/include/linux/bio.h
> +++ b/include/linux/bio.h
> @@ -365,7 +365,7 @@ extern struct bio *bio_copy_user_iov(struct request_queue *, struct sg_iovec *,
> extern int bio_uncopy_user(struct bio *);
> void zero_fill_bio(struct bio *bio);
> extern struct bio_vec *bvec_alloc_bs(gfp_t, int, unsigned long *, struct bio_set *);
> -extern inline unsigned int bvec_nr_vecs(unsigned short idx);
> +extern unsigned int bvec_nr_vecs(unsigned short idx);
>
> /*
> * bio_set is used to allow other portions of the IO system to
>
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
next prev parent reply other threads:[~2008-06-30 18:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 14:16 linux-next: Tree for June 30 Stephen Rothwell
2008-06-30 16:02 ` [BUILD-FAILURE] " Kamalesh Babulal
2008-06-30 16:43 ` Kamalesh Babulal
2008-06-30 18:59 ` Sam Ravnborg
2008-06-30 19:26 ` Ingo Molnar
2008-06-30 19:47 ` Sam Ravnborg
2008-06-30 20:06 ` Ingo Molnar
2008-06-30 20:11 ` Ingo Molnar
2008-06-30 20:25 ` Sam Ravnborg
2008-06-30 20:37 ` H. Peter Anvin
2008-06-30 20:42 ` H. Peter Anvin
2008-06-30 21:46 ` H. Peter Anvin
2008-07-01 2:10 ` Vivek Goyal
2008-07-01 6:56 ` Ingo Molnar
2008-07-01 8:15 ` Eric W. Biederman
2008-07-01 9:21 ` Kamalesh Babulal
2008-06-30 17:59 ` Jens Axboe
2008-06-30 18:21 ` Kamalesh Babulal [this message]
2008-06-30 18:25 ` [BUILD-FAILURE] linux-next: Tree for June 30 - powerpc - build failure at arch_add_memory() Kamalesh Babulal
2008-07-01 1:34 ` Tony Breeds
2008-07-01 8:04 ` Kamalesh Babulal
2008-06-30 18:43 ` linux-next: Tree for June 30 (USB: cdc-acm) Randy Dunlap
2008-06-30 19:01 ` Greg KH
2008-06-30 19:32 ` Alan Stern
2008-07-01 12:22 ` Oliver Neukum
2008-07-01 17:10 ` Oliver Neukum
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=4869240C.9060503@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=apw@shadowen.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).