The patch titled fault injection: correct function names in documentation has been removed from the -mm tree. Its filename was fault-injection-correct-function-names-in-documentation.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/ ------------------------------------------------------ Subject: fault injection: correct function names in documentation From: Anton Blanchard <anton@xxxxxxxxx> init_fault_attr_entries() should be init_fault_attr_dentries(). cleanup_fault_attr_entries() should be cleanup_fault_attr_dentries(). Signed-off-by: Anton Blanchard <anton@xxxxxxxxx> Acked-by: Akinobu Mita <akinobu.mita@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/fault-injection/fault-injection.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN Documentation/fault-injection/fault-injection.txt~fault-injection-correct-function-names-in-documentation Documentation/fault-injection/fault-injection.txt --- a/Documentation/fault-injection/fault-injection.txt~fault-injection-correct-function-names-in-documentation +++ a/Documentation/fault-injection/fault-injection.txt @@ -143,8 +143,8 @@ o provide a way to configure fault attri failslab, fail_page_alloc, and fail_make_request use this way. Helper functions: - init_fault_attr_entries(entries, attr, name); - void cleanup_fault_attr_entries(entries); + init_fault_attr_dentries(entries, attr, name); + void cleanup_fault_attr_dentries(entries); - module parameters _ Patches currently in -mm which might be from anton@xxxxxxxxx are origin.patch linux-next.patch percpu_counter-make-__percpu_counter_add-an-inline-function-on-up.patch sched-cpuacct-use-bigger-percpu-counter-batch-values-for-stats-counters.patch panic-fix-panic_timeout-accuracy-when-running-on-a-hypervisor.patch zlib-make-new-optimized-inflate-endian-independent.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