From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build error after merge of the kgdb tree
Date: Sat, 07 Aug 2010 06:09:35 -0500 [thread overview]
Message-ID: <4C5D3EEF.2080806@windriver.com> (raw)
In-Reply-To: <20100807142122.a305ed8a.sfr@canb.auug.org.au>
On 08/06/2010 11:21 PM, Stephen Rothwell wrote:
> Hi Jason,
>
> After merging the kgdb tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this error (and hundreds of similar
> errors/warnings):
>
> In file included from include/linux/rculist.h:10,
> from include/linux/dcache.h:6,
> from include/linux/fs.h:375,
> from include/linux/security.h:25,
> from security/min_addr.c:3:
> include/linux/rcupdate.h:606: warning: function declaration isn't a prototype
>
>
I removed the kgdb rcu stall detector patches from the queue until they
are re-worked against the latest rcu changes pending in linux-next.
Thanks,
Jason.
prev parent reply other threads:[~2010-08-07 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 4:21 linux-next: build error after merge of the kgdb tree Stephen Rothwell
2010-08-07 11:09 ` Jason Wessel [this message]
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=4C5D3EEF.2080806@windriver.com \
--to=jason.wessel@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.