From: Jens Axboe <jens.axboe@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: block/rcu merge build failure
Date: Fri, 13 Jun 2008 09:18:04 +0200 [thread overview]
Message-ID: <20080613071803.GT20851@kernel.dk> (raw)
In-Reply-To: <20080613171351.9ad7e1df.sfr@canb.auug.org.au>
On Fri, Jun 13 2008, Stephen Rothwell wrote:
> Hi Jens,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> kernel/smp.c: In function 'generic_smp_call_function_interrupt':
> kernel/smp.c:106: error: implicit declaration of function 'list_for_each_entry_rcu'
>
> This is caused by the merge of the rcu tree (contained in sched tree)
> with the block tree. I have applied the following patch which I will
> carry as part of the block tree merge commit.
That patch is fine, I guess there's an rcu include splitup patch in
-next which clashes with this a bit. Thanks Stephen.
--
Jens Axboe
next prev parent reply other threads:[~2008-06-13 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 7:13 linux-next: block/rcu merge build failure Stephen Rothwell
2008-06-13 7:18 ` Jens Axboe [this message]
2008-06-13 7:31 ` 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=20080613071803.GT20851@kernel.dk \
--to=jens.axboe@oracle$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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