From: Jani Monoses <jani@virtualro.ic.ro>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: inode.c inline doc fix
Date: Sat, 16 Dec 2000 14:35:28 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.10.10012161432001.10586-100000@virtualro.ic.ro> (raw)
Hi Linus,
this adds (hopefully correct) documentation to the newly
intorduced flags parameter in mark_inode_dirty.
--- /usr/src/linux/fs/inode.c Tue Dec 12 11:25:55 2000
+++ inode.c Sat Dec 16 14:38:25 2000
@@ -125,8 +125,9 @@
/**
* __mark_inode_dirty - internal function
* @inode: inode to mark
- *
- * Mark an inode as dirty. Callers should use mark_inode_dirty.
+ * @flags: what kind of dirty (i.e. I_DIRTY_SYNC)
+ * Mark an inode as dirty. 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-16 13:07 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.10012161432001.10586-100000@virtualro.ic.ro \
--to=jani@virtualro.ic.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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).