public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-doc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Documentation: seq_file: drop 2.6 reference
Date: Fri, 10 Apr 2026 08:39:47 -0600	[thread overview]
Message-ID: <87zf3a2824.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260410143234.43610-2-wsa+renesas@sang-engineering.com>

Wolfram Sang <wsa+renesas@sang-engineering.com> writes:

> Even kernels after 2.6 have seq-file support.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> See, somebody still reads it :)
>
>  Documentation/filesystems/seq_file.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/seq_file.rst b/Documentation/filesystems/seq_file.rst
> index 1e1713d00010..d753d8177bcb 100644
> --- a/Documentation/filesystems/seq_file.rst
> +++ b/Documentation/filesystems/seq_file.rst
> @@ -27,7 +27,7 @@ position within the virtual file - that position is, likely as not, in the
>  middle of a line of output. The kernel has traditionally had a number of
>  implementations that got this wrong.
>  
> -The 2.6 kernel contains a set of functions (implemented by Alexander Viro)
> +The kernel now contains a set of functions (implemented by Alexander Viro)
>  which are designed to make it easy for virtual file creators to get it

But but but ... it *is* correct as written... :)

(Applied, thanks).

jon

      reply	other threads:[~2026-04-10 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 14:31 [PATCH] Documentation: seq_file: drop 2.6 reference Wolfram Sang
2026-04-10 14:39 ` Jonathan Corbet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zf3a2824.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=wsa+renesas@sang-engineering.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox