From: ebiederm@xmission•com (Eric W. Biederman)
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the namespace tree
Date: Tue, 10 May 2011 21:21:12 -0700 [thread overview]
Message-ID: <m1hb91eukn.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20110511140900.bbafb560.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Wed, 11 May 2011 14:09:00 +1000")
Stephen Rothwell <sfr@canb•auug.org.au> writes:
> Hi Eric,
>
> After merging the namespace tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> In file included from arch/powerpc/platforms/cell/spu_callbacks.c:49:
> arch/powerpc/include/asm/systbl.h:356: error: 'sys_setns' undeclared here (not in a function)
>
> Caused by commit e975ee91dcc1 ("ns: Wire up the setns system call").
> sys_setns should be declared in include/linux/syscalls.h.
>
> I have dropped the namespace tree for today.
Ouch. I guess I must have missed something I will take a look.
My apologies for the trouble.
Eric
prev parent reply other threads:[~2011-05-11 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 4:09 linux-next: build failure after merge of the namespace tree Stephen Rothwell
2011-05-11 4:21 ` Eric W. Biederman [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=m1hb91eukn.fsf@fess.ebiederm.org \
--to=ebiederm@xmission$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--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