The patch titled Subject: ceph/mds_client.c: quiet sparse noise has been removed from the -mm tree. Its filename was ceph-mds_clientc-quiet-sparse-noise.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ From: H Hartley Sweeten <hartleys@xxxxxxxxxxxxxxxxxxx> Subject: ceph/mds_client.c: quiet sparse noise warning: symbol 'get_nonsnap_parent' was not declared. Should it be static? warning: symbol 'done_closing_sessions' was not declared. Should it be static? Local functions don't need external visability. Make them static. Signed-off-by: H Hartley Sweeten <hsweeten@xxxxxxxxxxxxxxxxxxx> Cc: Sage Weil <sage@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/ceph/mds_client.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN fs/ceph/mds_client.c~ceph-mds_clientc-quiet-sparse-noise fs/ceph/mds_client.c --- a/fs/ceph/mds_client.c~ceph-mds_clientc-quiet-sparse-noise +++ a/fs/ceph/mds_client.c @@ -619,7 +619,7 @@ static void __unregister_request(struct * * Called under mdsc->mutex. */ -struct dentry *get_nonsnap_parent(struct dentry *dentry) +static struct dentry *get_nonsnap_parent(struct dentry *dentry) { /* * we don't need to worry about protecting the d_parent access @@ -3154,7 +3154,7 @@ void ceph_mdsc_sync(struct ceph_mds_clie /* * true if all sessions are closed, or we force unmount */ -bool done_closing_sessions(struct ceph_mds_client *mdsc) +static bool done_closing_sessions(struct ceph_mds_client *mdsc) { int i, n = 0; _ Patches currently in -mm which might be from hartleys@xxxxxxxxxxxxxxxxxxx are origin.patch arch-x86-kernel-e820c-quiet-sparse-noise-about-plain-integer-as-null-pointer.patch arch-x86-kernel-ptracec-quiet-sparse-noise.patch arch-x86-mm-pageattrc-quiet-sparse-noise-local-functions-should-be-static.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html