From: "Jérémy Cochoy" <jeremy.cochoy@gmail.com>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Pavel Machek <pavel@suse.cz>,
Al Viro <viro@zeniv.linux.org.uk>,
ronny.pretzsch@dfs.de, Corentin Chary <corentin.chary@gmail.com>
Subject: [PATCH] fs/ext2: ext2_readdir comment about returns
Date: Mon, 30 Nov 2009 00:30:55 +0100 [thread overview]
Message-ID: <a229bc400911291530s51e1971do402e6441115d70ee@mail.gmail.com> (raw)
From:Jeremy Cochoy <jeremy.cochoy@gmail.com>
Hello,
I submit a short correction about a comment in ext2/dir.c
(I've already send it but it wasn't the good patch format and i didn't
cc the right people.)
PS: Please excuse me if I make mistakes with the netiquette, it's my
first patch and i wich to send more useful patchs next time, without
hurting your eyes.
Best regards,
-----
diff --git a/fs/ext2/dir.c b/fs/ext2/dir.c
index 6cde970..fc2bd05 100644
--- a/fs/ext2/dir.c
+++ b/fs/ext2/dir.c
@@ -353,8 +353,8 @@ ext2_readdir (struct file * filp, void * dirent,
filldir_t filldir)
* ext2_find_entry()
*
* finds an entry in the specified directory with the wanted name. It
- * returns the page in which the entry was found, and the entry itself
- * (as a parameter - res_dir). Page is returned mapped and unlocked.
+ * returns the page in which the entry was found (as a parameter - res_page),
+ * and the entry itself. Page is returned mapped and unlocked.
* Entry is guaranteed to be valid.
*/
struct ext2_dir_entry_2 *ext2_find_entry (struct inode * dir,
--
Jérémy Cochoy - L1 MI (Lyon1)
Mail : jeremy.cochoy@gmail.com
Tel : 06-43-01-74-02
Alias Zenol - http://zenol.fr
next reply other threads:[~2009-11-29 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 23:30 Jérémy Cochoy [this message]
2009-11-30 11:17 ` Jan Kara
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=a229bc400911291530s51e1971do402e6441115d70ee@mail.gmail.com \
--to=jeremy.cochoy@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corentin.chary@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=ronny.pretzsch@dfs.de \
--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®