The patch titled
Subject: seq_file-document-how-per-entry-resources-are-managed-fix
has been removed from the -mm tree. Its filename was
seq_file-document-how-per-entry-resources-are-managed-fix.patch
This patch was dropped because it was folded into seq_file-document-how-per-entry-resources-are-managed.patch
------------------------------------------------------
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: seq_file-document-how-per-entry-resources-are-managed-fix
fix typo, per Willy
Cc: NeilBrown <neilb@xxxxxxx>
Cc: Matthew Wilcox <willy@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/filesystems/seq_file.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/Documentation/filesystems/seq_file.rst~seq_file-document-how-per-entry-resources-are-managed-fix
+++ a/Documentation/filesystems/seq_file.rst
@@ -218,7 +218,7 @@ is a reasonable thing to do. The seq_fil
other locks while the iterator is active.
The iterater value returned by start() or next() is guaranteed to be
-passed to a subsequenct next() or stop() call. This allows resources
+passed to a subsequent next() or stop() call. This allows resources
such as locks that were taken to be reliably released. There is *no*
guarantee that the iterator will be passed to show(), though in practice
it often will be.
_
Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are
seq_file-document-how-per-entry-resources-are-managed.patch
initramfs-panic-with-memory-information-fix.patch
mm-page_allocc-refactor-initialization-of-struct-page-for-holes-in-memory-layout-fix.patch
mm.patch
mm-vmstat-fix-proc-sys-vm-stat_refresh-generating-false-warnings-fix-2.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
kernel-forkc-export-kernel_thread-to-modules.patch
