mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Christian Brauner <brauner@kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>, NeilBrown <neil@brown.name>,
	Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH] fs: porting: Retitle
Date: Mon, 16 Nov 2026 20:02:11 -0800	[thread overview]
Message-ID: <c5d64937-b75f-4795-b3e3-7d15cd5e7e9e@infradead.org> (raw)
In-Reply-To: <20261117035004.12262-1-bagasdotme@gmail.com>



On 11/16/26 7:50 PM, Bagas Sanjaya wrote:
> porting.rst is a technical reference on what changes to the fs subsystem
> (since 2.5.0), not the whole kernel as the existing title may imply.
> 
> Retitle it.
> 
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.

> ---
>  Documentation/filesystems/porting.rst | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/filesystems/porting.rst b/Documentation/filesystems/porting.rst
> index c38f5df755bb50..dd5a55e68ba7b6 100644
> --- a/Documentation/filesystems/porting.rst
> +++ b/Documentation/filesystems/porting.rst
> @@ -1,6 +1,8 @@
> -====================
> -Changes since 2.5.0:
> -====================
> +=============================
> +Filesystems API Porting Guide
> +=============================
> +
> +This document details changes to the filesystem subsystem.
>  
>  ---
>  
> 
> base-commit: 2138148bf44fd84d3e0a863f0e8cb3627cdcc606

-- 
~Randy

      reply	other threads:[~2026-11-17  4:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  3:50 Bagas Sanjaya
2026-11-17  4:02 ` Randy Dunlap [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=c5d64937-b75f-4795-b3e3-7d15cd5e7e9e@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bagasdotme@gmail.com \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=sandeen@redhat.com \
    --cc=skhan@linuxfoundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®