From: Oleg Nesterov <oleg@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Tejun Heo <tj@kernel.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Fleming <matt.fleming@intel.com>
Subject: Re: linux-next: build failure after merge of the ptrace tree
Date: Thu, 25 Aug 2011 16:37:58 +0200 [thread overview]
Message-ID: <20110825143758.GA2039@redhat.com> (raw)
In-Reply-To: <20110825141212.4f82835beaad506553e291e8@canb.auug.org.au>
Hi Stephen,
On 08/25, Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the ptrace tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> ERROR: ".set_current_blocked" [fs/autofs4/autofs4.ko] undefined!
In case you didn't notice, we are doing our best to complicate
your life :/
Sorry.
> Presumably set_current_blocked() needs to be EXPORTed.
Yes. I've reset the last 4 commits which touch the code in fs/.
Will add them back after the patch which exports set_current_blocked.
Thanks a lot!
Oleg.
prev parent reply other threads:[~2011-08-25 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 4:12 linux-next: build failure after merge of the ptrace tree Stephen Rothwell
2011-08-25 14:37 ` Oleg Nesterov [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=20110825143758.GA2039@redhat.com \
--to=oleg@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
/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).