All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolai Stange <nicstange@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Nicolai Stange <nicstange@gmail.com>
Subject: [PATCH 1/2] debugfs: fix DocBook comment of debugfs_use_file_start()
Date: Sun,  6 Mar 2016 20:59:04 +0100	[thread overview]
Message-ID: <1457294345-4588-2-git-send-email-nicstange@gmail.com> (raw)
In-Reply-To: <1457294345-4588-1-git-send-email-nicstange@gmail.com>

In commit 055cd38ba671 ("debugfs: prevent access to possibly dead
                         file_operations at file open")
debugfs_use_file_start() has been introduced. Unfortunately, the associated
DocBook comment hasn't been updated to properly reflect the change of the
'file' argument into 'dentry' during the evolution of the aforementioned
patch.

Catch up on this and rename '@file' to '@dentry' in the DocBook comment
associated with debugfs_use_file_start().

Signed-off-by: Nicolai Stange <nicstange@gmail.com>
---
 fs/debugfs/file.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
index 1a03e99..6a4b667 100644
--- a/fs/debugfs/file.c
+++ b/fs/debugfs/file.c
@@ -50,7 +50,7 @@ const struct file_operations debugfs_noop_file_operations = {
 
 /**
  * debugfs_use_file_start - mark the beginning of file data access
- * @file: the file object whose data is being accessed.
+ * @dentry: the dentry object whose data is being accessed.
  * @srcu_idx: a pointer to some memory to store a SRCU index in.
  *
  * Up to a matching call to debugfs_use_file_finish(), any
-- 
2.7.2

  reply	other threads:[~2016-03-06 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06 19:59 [PATCH 0/2] debugfs: fixup to file removal protection series Nicolai Stange
2016-03-06 19:59 ` Nicolai Stange [this message]
2016-03-06 19:59 ` [PATCH 2/2] debugfs: inline dummy implementations of debugfs_use_file_start()/_finish() Nicolai Stange
2016-03-22 13:17 ` [PATCH 0/2] debugfs: fixup to file removal protection series Nicolai Stange

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=1457294345-4588-2-git-send-email-nicstange@gmail.com \
    --to=nicstange@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.