mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Filesystems Development <linux-fsdevel@vger.kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Mateusz Guzik <mjguzik@gmail.com>,
	Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
	Amir Goldstein <amir73il@gmail.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/2] vfs kernel-doc fixes for 6.19
Date: Fri, 19 Dec 2025 09:46:18 +0700	[thread overview]
Message-ID: <20251219024620.22880-1-bagasdotme@gmail.com> (raw)

Hi,

Here are kernel-doc fixes for vfs subsystem targetting 6.19. This small
series is split from much larger kernel-doc fixes series I posted a while
ago [1].

Enjoy!

[1]: https://lore.kernel.org/linux-fsdevel/20251215113903.46555-1-bagasdotme@gmail.com/

Bagas Sanjaya (2):
  fs: Describe @isnew parameter in ilookup5_nowait()
  VFS: fix __start_dirop() kernel-doc warnings

 fs/inode.c | 3 +++
 fs/namei.c | 3 ++-
 2 files changed, 5 insertions(+), 1 deletion(-)


base-commit: 24835a96f21ebb295d24e265b5466d9e40f12cbd
-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2025-12-19  4:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19  2:46 Bagas Sanjaya [this message]
2025-12-19  2:46 ` [PATCH 1/2] fs: Describe @isnew parameter in ilookup5_nowait() Bagas Sanjaya
2025-12-19 13:50   ` Jan Kara
2025-12-19 14:52   ` Jeff Layton
2025-12-19  2:46 ` [PATCH 2/2] VFS: fix __start_dirop() kernel-doc warnings Bagas Sanjaya
2025-12-19 13:51   ` Jan Kara
2025-12-19 14:52   ` Jeff Layton
2025-12-27  4:45   ` NeilBrown
2025-12-24 12:33 ` [PATCH 0/2] vfs kernel-doc fixes for 6.19 Christian Brauner
2026-01-06 22:51 ` Christian Brauner

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=20251219024620.22880-1-bagasdotme@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=neil@brown.name \
    --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®