From: Jani Monoses <jani@virtualro.ic.ro>
To: twaugh@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: [patch] inode.c doc fix
Date: Mon, 18 Dec 2000 16:07:26 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.10.10012181605000.14823-100000@virtualro.ic.ro> (raw)
Hi
here's a patch for documenting the newly introduced flags field
in mark_inode_dirty().
Jani.
--- /usr/src/linux/fs/inode.c Mon Dec 18 15:57:34 2000
+++ inode.c Mon Dec 18 16:08:14 2000
@@ -125,8 +125,10 @@
/**
* __mark_inode_dirty - internal function
* @inode: inode to mark
+ * @flags: dirty flag mask (i.e. I_DIRTY)
*
- * Mark an inode as dirty. Callers should use mark_inode_dirty.
+ * Mark an inode as dirty by setting the specified flags in the inode's i_state field.
+ * Callers should use mark_inode_dirty() or mark_inode_dirty_sync().
*/
void __mark_inode_dirty(struct inode *inode, int flags)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-18 14:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.10.10012181605000.14823-100000@virtualro.ic.ro \
--to=jani@virtualro.ic.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=twaugh@redhat.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;
as well as URLs for NNTP newsgroup(s).