From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Ian Kent <ikent@redhat.com>
Subject: linux-next: manual merge of the akpm tree with the vfs tree
Date: Mon, 12 Dec 2016 16:52:07 +1100 [thread overview]
Message-ID: <20161212165207.48c149de@canb.auug.org.au> (raw)
Hi all,
Al let me know that he had put a newer version of the autofs patches
into his vfs tree, so I have dropped the following patches from the akpm
tree today:
vfs: change d_manage() to take a struct path
vfs: add path_is_mountpoint() helper
vfs: fix boolreturn.cocci warnings
vfs: add path_has_submounts()
autofs: change autofs4_expire_wait() to take struct path
autofs: change autofs4_wait() to take struct path
autofs: use path_is_mountpoint() to fix unreliable d_mountpoint() checks
autofs: use path_has_submounts() to fix unreliable have_submount() checks
vfs: remove unused have_submounts() function
vfs: merge path_is_mountpoint() and path_is_mountpoint_rcu()
autofs: make struct path const in autofs4_dir_open()
autofs: change struct path to const in autofs4_expire_wait() and autofs4_wait()
vfs: change struct path to const in d_manage()
vfs: constify path parameter of path_has_submounts()
autofs: don't hold spinlock over direct mount expire
vfs: make may_umount_tree() mount propagation aware
vfs-make-may_umount_tree-mount-propogation-aware-checkpatch-fixes
I hope that was the correct ones.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-12-12 5:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 5:52 Stephen Rothwell [this message]
2016-12-12 8:14 ` linux-next: manual merge of the akpm tree with the vfs tree Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2020-05-15 11:33 Stephen Rothwell
2019-04-11 6:21 Stephen Rothwell
2018-05-17 6:36 Stephen Rothwell
2018-01-02 6:46 Stephen Rothwell
2014-08-08 6:20 Stephen Rothwell
2013-09-10 4:41 Stephen Rothwell
2013-09-05 8:56 Stephen Rothwell
2013-04-30 5:54 Stephen Rothwell
2013-04-29 8:34 Stephen Rothwell
2013-04-29 8:25 Stephen Rothwell
2013-04-04 6:26 Stephen Rothwell
2013-04-04 6:56 ` Andrew Morton
2013-04-04 7:02 ` Andrew Morton
2013-04-04 8:10 ` Al Viro
2013-04-04 23:18 ` Stephen Rothwell
2013-04-04 8:02 ` Al Viro
2013-04-04 15:43 ` Nathan Zimmer
2013-04-04 6:17 Stephen Rothwell
2013-04-04 6:12 Stephen Rothwell
2013-04-04 12:33 ` Jan Kara
2013-04-04 6:04 Stephen Rothwell
2013-02-25 3:40 Stephen Rothwell
2012-09-24 13:40 Stephen Rothwell
2012-09-24 13:12 Stephen Rothwell
2012-09-24 13:06 Stephen Rothwell
2012-07-22 5:44 Stephen Rothwell
2011-07-18 8:55 Stephen Rothwell
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=20161212165207.48c149de@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=ikent@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).