The patch titled efs: add entry for EFS filesystem to MAINTAINERS as Orphan has been removed from the -mm tree. Its filename is add-entry-for-efs-filesystem-to-maintainers-as-orphan.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ Subject: efs: add entry for EFS filesystem to MAINTAINERS as Orphan From: Josh Triplett <josht@xxxxxxxxxx> The EFS filesystem does not have an entry in MAINTAINERS; add one, giving the EFS filesystem and listing the status as Orphan, per the note on that page saying "I'm no longer actively maintaining EFS". Signed-off-by: Josh Triplett <josh@xxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- MAINTAINERS | 4 ++++ 1 file changed, 4 insertions(+) diff -puN MAINTAINERS~add-entry-for-efs-filesystem-to-maintainers-as-orphan MAINTAINERS --- a/MAINTAINERS~add-entry-for-efs-filesystem-to-maintainers-as-orphan +++ a/MAINTAINERS @@ -968,6 +968,10 @@ P: Andrey V. Savochkin M: saw@xxxxxxxxxxxxx S: Maintained +EFS FILESYSTEM +W: http://aeschi.ch.eu.org/efs/ +S: Orphan + EMU10K1 SOUND DRIVER P: James Courtier-Dutton M: James@xxxxxxxxxxxxxxxxxxxx _ Patches currently in -mm which might be from josht@xxxxxxxxxx are origin.patch git-nfs.patch xfs-add-lock-annotations-to-xfs_trans_update_ail-and-xfs_trans_delete_ail.patch efi-add-lock-annotations-for-efi_call_phys_prelog-and-efi_call_phys_epilog.patch mbcache-add-lock-annotation-for-__mb_cache_entry_release_unlock.patch afs-add-lock-annotations-to-afs_proc_cell_servers_startstop.patch fuse-add-lock-annotations-to-request_end-and-fuse_read_interrupt.patch hugetlbfs-add-lock-annotation-to-hugetlbfs_forget_inode.patch jbd-add-lock-annotation-to-jbd_sync_bh.patch fs-add-lock-annotation-to-grab_super.patch rcu-add-lock-annotations-to-rcu_bh_torture_read_lockunlock.patch timer-add-lock-annotation-to-lock_timer_base.patch nfsd-add-lock-annotations-to-e_start-and-e_stop.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