From: Omar Sandoval <osandov@osandov.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Ian Kent <raven@themaw.net>,
autofs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: Autofs and mount namespaces
Date: Thu, 7 Apr 2016 12:42:35 -0700 [thread overview]
Message-ID: <20160407194235.GA18275@vader> (raw)
In-Reply-To: <201604080354.YGshLn7u%fengguang.wu@intel.com>
On Fri, Apr 08, 2016 at 03:08:42AM +0800, kbuild test robot wrote:
> Hi Omar,
>
> [auto build test ERROR on v4.6-rc2]
> [also build test ERROR on next-20160407]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/Omar-Sandoval/Autofs-and-mount-namespaces/20160408-022034
> config: i386-randconfig-i0-201614 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "lookup_mnt" [fs/autofs4/autofs4.ko] undefined!
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
Oh, yeah, that needs an EXPORT_SYMBOL(lookup_mnt).
--
Omar
next prev parent reply other threads:[~2016-04-07 19:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 18:19 Autofs and mount namespaces Omar Sandoval
2016-04-07 19:08 ` kbuild test robot
2016-04-07 19:42 ` Omar Sandoval [this message]
2016-04-08 0:51 ` Ian Kent
2016-04-08 1:04 ` Ian Kent
2016-04-08 20:21 ` Omar Sandoval
2016-04-10 2:53 ` Ian Kent
2016-07-05 18:47 ` Omar Sandoval
2016-07-05 23:35 ` Ian Kent
2016-09-13 18:19 ` Omar Sandoval
2016-09-14 0:56 ` Ian Kent
2016-09-14 1:25 ` Omar Sandoval
2016-04-08 1:21 ` Ian Kent
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=20160407194235.GA18275@vader \
--to=osandov@osandov.com \
--cc=autofs@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=raven@themaw.net \
/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).