* + seq_file-document-how-per-entry-resources-are-managed-fix.patch added to -mm tree
@ 2021-02-05 22:40 akpm
0 siblings, 0 replies; only message in thread
From: akpm @ 2021-02-05 22:40 UTC (permalink / raw)
To: akpm, mm-commits, neilb, willy
The patch titled
Subject: seq_file-document-how-per-entry-resources-are-managed-fix
has been added to the -mm tree. Its filename is
seq_file-document-how-per-entry-resources-are-managed-fix.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/seq_file-document-how-per-entry-resources-are-managed-fix.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/seq_file-document-how-per-entry-resources-are-managed-fix.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: seq_file-document-how-per-entry-resources-are-managed-fix
fix typo, per Willy
Cc: NeilBrown <neilb@suse.de>
Cc: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
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@linux-foundation.org are
mm.patch
mm-memcg-slab-pre-allocate-obj_cgroups-for-slab-caches-with-slab_account-fix.patch
mm-memcontrol-optimize-per-lruvec-stats-counter-memory-usage-checkpatch-fixes.patch
mm-memcg-add-swapcache-stat-for-memcg-v2-fix.patch
kasan-add-match-all-tag-tests-fix-fix.patch
mm-cma-allocate-cma-areas-bottom-up-fix-3-fix.patch
mm-vmstat-fix-proc-sys-vm-stat_refresh-generating-false-warnings-fix-2.patch
bdi-use-might_alloc-fix.patch
kfence-kasan-make-kfence-compatible-with-kasan-fix.patch
lib-stackdepot-add-support-to-disable-stack-depot-fix.patch
seq_file-document-how-per-entry-resources-are-managed-fix.patch
initramfs-panic-with-memory-information-fix.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
fs-ramfs-inodec-update-inode_operationstmpfile.patch
kernel-forkc-export-kernel_thread-to-modules.patch
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-02-06 3:07 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-05 22:40 + seq_file-document-how-per-entry-resources-are-managed-fix.patch added to -mm tree akpm
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.