linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <ikent@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [vfs:work.autofs 6/10] ERROR: "path_is_mountpoint" [fs/autofs4/autofs4.ko] undefined!
Date: Mon, 05 Dec 2016 07:31:07 +0800	[thread overview]
Message-ID: <1480894267.3781.1.camel@redhat.com> (raw)
In-Reply-To: <20161204152308.GF1555@ZenIV.linux.org.uk>

On Sun, 2016-12-04 at 15:23 +0000, Al Viro wrote:
> On Sun, Dec 04, 2016 at 05:28:08PM +0800, Ian Kent wrote:
> 
> > 
> > Oh wait, I did see this when I looked at vfs.git#work.autofs but was more
> > concerned with the substance of the changes to pay attention to it.
> > 
> > That would be caused by:
> > bool path_is_mountpoint(const struct path *path)
> > {
> > ...
> > }
> > EXPORT_SYMBOL(__path_is_mountpoint);
> Had been fixed and pushed yesterday.

I missed it when I built my test kernel because I compile in the autofs module,
;)

Ian

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2016-12-04 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-04  1:04 [vfs:work.autofs 6/10] ERROR: "path_is_mountpoint" [fs/autofs4/autofs4.ko] undefined! kbuild test robot
2016-12-04  9:28 ` Ian Kent
2016-12-04 15:23   ` Al Viro
2016-12-04 23:31     ` Ian Kent [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=1480894267.3781.1.camel@redhat.com \
    --to=ikent@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).