From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Hok Chun NG (Ben)" <me@benbenng.net>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Update documentation of vfs_tmpfile
Date: Tue, 21 Feb 2023 20:21:58 +0700 [thread overview]
Message-ID: <Y/TFdmhvrLu1h8Kl@debian.me> (raw)
In-Reply-To: <01000186721d17f8-ab0c64f0-a6ae-4e43-99a3-a44e6dba95b6-000000@email.amazonses.com>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
On Tue, Feb 21, 2023 at 03:55:54AM +0000, Hok Chun NG (Ben) wrote:
> On function vfs_tmpfile, documentation is updated according to function signature update.
>
> Description for 'dentry' and 'open_flag' removed.
> Description for 'parentpath' and 'file' added.
What commit did vfs_tmpfile() change its signature?
For the patch description, I'd like to write "Commit <commit> changes
function signature for vfs_tmpfile(). Catch the function documentation
up with the change."
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-02-21 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230221035528.10529-1-me@benbenng.net>
2023-02-21 3:55 ` [PATCH] Update documentation of vfs_tmpfile Hok Chun NG (Ben)
2023-02-21 13:21 ` Bagas Sanjaya [this message]
2023-02-22 1:15 ` Hok Chun NG (Ben)
2023-02-22 2:32 ` Bagas Sanjaya
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=Y/TFdmhvrLu1h8Kl@debian.me \
--to=bagasdotme@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@benbenng.net \
--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