From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@ZenIV•linux.org.uk>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: Signed-off-by missing for commits in the vfs tree
Date: Tue, 18 Dec 2018 10:38:10 +1100 [thread overview]
Message-ID: <20181218103810.11687f68@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]
Hi Al,
Commits
c1cae12e6b4a ("vfs: Add a sample program for the new mount API")
d101a34a2c79 ("vfs: syscall: Add fspick() to select a superblock for reconfiguration")
1fcae4c630e3 ("vfs: syscall: Add fsmount() to create a mount for a superblock")
ec4256de39c3 ("vfs: syscall: Add fsconfig() for configuring and managing a context")
0cba0050bcbe ("vfs: Implement logging through fs_context")
4552c960ff40 ("vfs: syscall: Add fsopen() to prepare for superblock creation")
03ca430a2648 ("Make anon_inodes unconditional")
96298884c8b4 ("vfs: syscall: Add move_mount(2) to move mounts around")
6c606fff6c91 ("afs: Use fs_context to pass parameters over automount")
10424811186f ("afs: Add fs_context support")
8fa5366945d8 ("vfs: Add some logging to the core users of the fs_context log")
8907f3967fbc ("vfs: Implement logging through fs_context")
bed15a150f44 ("vfs: Provide documentation for new mount API")
460375e70621 ("vfs: Remove kern_mount_data()")
e88bea43b477 ("hugetlbfs: Convert to fs_context")
d48db7fb30db ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context")
35822336b482 ("cpuset: Use fs_context")
b97c89323b7b ("ipc: Convert mqueue fs to fs_context")
e1f97a645981 ("proc: Add fs_context support to procfs")
5aed868ddf7f ("procfs: Move proc_fill_super() to fs/proc/root.c")
013c7af575e5 ("vfs: Implement a filesystem superblock creation/configuration context")
47173883ff4d ("tomoyo: Implement security hooks for the new mount API")
c36d02347290 ("apparmor: Implement security hooks for the new mount API")
18ee890db905 ("vfs: Put security flags into the fs_context struct")
18ef962eeec1 ("vfs: Add LSM hooks for the new mount API")
1bff8b546644 ("vfs: Add configuration parser helpers")
57fb096cd685 ("vfs: Introduce logging functions")
23ac0033ae3c ("vfs: Introduce the basic header for the new mount API's filesystem context")
0a8054c863b8 ("vfs: Separate changing mount flags full remount")
e322b9267880 ("vfs: Suppress MS_* flag defs within the kernel unless explicitly enabled")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-12-17 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 23:38 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-20 20:45 linux-next: Signed-off-by missing for commits in the vfs tree Stephen Rothwell
2018-12-20 21:05 ` Al Viro
2018-12-20 21:10 ` Stephen Rothwell
2018-07-18 13:21 Stephen Rothwell
2018-06-16 6:48 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=20181218103810.11687f68@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/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