Re: [PATCH 1/3] seq_file: document how per-entry resources are managed.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: NeilBrown <neilb@xxxxxxx>
Subject: Re: [PATCH 1/3] seq_file: document how per-entry resources are managed.
From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
Date: Fri, 5 Feb 2021 02:20:24 +0000
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, Jonathan Corbet <corbet@xxxxxxx>, Xin Long <lucien.xin@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-doc@xxxxxxxxxxxxxxx
In-reply-to: <161248539020.21478.3147971477400875336.stgit@noble1>
References: <161248518659.21478.2484341937387294998.stgit@noble1> <161248539020.21478.3147971477400875336.stgit@noble1>

On Fri, Feb 05, 2021 at 11:36:30AM +1100, NeilBrown wrote:
> +passed to a subsequenct next() or stop() call.  This allows resources

s/quenct/quent/

References:
- [PATCH 0/3] Fix some seq_file users that were recently broken
  - From: NeilBrown
- [PATCH 1/3] seq_file: document how per-entry resources are managed.
  - From: NeilBrown

Prev by Date: Re: [PATCH 0/2] docs: Add support for relative paths in automarkup
Next by Date: [PATCH v3 1/2] procfs: Allow reading fdinfo with PTRACE_MODE_READ
Previous by thread: [PATCH 1/3] seq_file: document how per-entry resources are managed.
Next by thread: Re: [PATCH 0/3] Fix some seq_file users that were recently broken
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]

Powered by Linux