From: Peter Zijlstra <peterz@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Huang Ying <ying.huang@intel.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the tip tree
Date: Wed, 05 Oct 2011 10:46:13 +0200 [thread overview]
Message-ID: <1317804373.6766.0.camel@twins> (raw)
In-Reply-To: <20111005172528.0d0a8afc65acef7ace22a24e@canb.auug.org.au>
On Wed, 2011-10-05 at 17:25 +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> net/rds/ib_rdma.c: In function 'rds_ib_reuse_fmr':
> net/rds/ib_rdma.c:272:2: error: implicit declaration of function 'llist_del_first' [-Werror=implicit-function-declaration]
> net/rds/ib_rdma.c:272:6: warning: assignment makes pointer from integer without a cast [enabled by default]
> net/rds/ib_rdma.c: In function 'rds_ib_flush_mr_pool':
> net/rds/ib_rdma.c:671:4: error: implicit declaration of function 'llist_add_batch' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
>
> Caused by commit 1230db8e1543 ("llist: Make some llist functions inline")
> interacting with commit 1bc144b62524 ("net, rds, Replace xlist in
> net/rds/xlist.h with llist") from the net tree. The former commit
> removes the declarations of llist_del_first() and llist_add_batch() with
> no explanation (and probably by accident since the definitions still
> exist).
Ugh yes, my bad. Ingo objected to inlining all those functions and I
then screwed up. There are no users of those two functions in my tree.
next prev parent reply other threads:[~2011-10-05 8:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 6:25 linux-next: build failure after merge of the tip tree Stephen Rothwell
2011-10-05 8:46 ` Peter Zijlstra [this message]
2011-10-11 6:15 ` Stephen Rothwell
[not found] <20150407171858.2ad46594@canb.auug.org.au>
[not found] ` <20150407084829.GA9577@gmail.com>
[not found] ` <55239BAD.6040304@iogearbox.net>
[not found] ` <20150407190527.1633a186@canb.auug.org.au>
[not found] ` <5523BBE0.8030400@iogearbox.net>
[not found] ` <55240342.9050900@plumgrid.com>
[not found] ` <552435DD.5040802@iogearbox.net>
[not found] ` <20150408150327.313be6a3@canb.auug.org.au>
2015-04-15 1:25 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2015-09-16 1:30 Stephen Rothwell
2015-09-16 4:53 ` David Miller
2016-11-17 3:22 Stephen Rothwell
2017-11-01 10:51 Stephen Rothwell
2017-11-01 14:32 ` Kees Cook
2018-04-03 5:41 Stephen Rothwell
2018-04-03 9:30 ` Peter Zijlstra
2018-04-03 12:39 ` David Howells
2018-04-03 12:42 ` Peter Zijlstra
2018-04-03 12:41 ` David Howells
[not found] <20190625160432.533aa140@canb.auug.org.au>
2019-07-09 3:46 ` Stephen Rothwell
2021-03-22 3:37 Stephen Rothwell
2021-03-22 9:00 ` Borislav Petkov
2021-03-26 8:57 ` Sedat Dilek
2021-03-26 13:11 ` Borislav Petkov
2021-03-27 11:50 ` Sedat Dilek
2021-03-27 21:26 ` Stephen Rothwell
2021-03-23 8:34 ` Sedat Dilek
2025-05-14 5:23 Stephen Rothwell
2025-05-14 5:38 ` Ingo Molnar
2025-05-28 3:56 ` 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=1317804373.6766.0.camel@twins \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).