From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Ravishankar N <cyberax82@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Namjae Jeon <linkinjeon@gmail.com>
Subject: Re: [PATCH 1/1] fat:fix incorrect function comment
Date: Thu, 20 Dec 2012 00:57:24 +0900 [thread overview]
Message-ID: <87ehimdogr.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1355849419-26403-1-git-send-email-cyberax82@gmail.com> (Ravishankar N.'s message of "Tue, 18 Dec 2012 22:20:19 +0530")
Ravishankar N <cyberax82@gmail.com> writes:
> /*
> - * Return values: negative -> error, 0 -> not found, positive -> found,
> - * value is the total amount of slots, including the shortname entry.
> + * Return values: negative -> error/not found, 0 -> found.
> */
> int fat_search_long(struct inode *inode, const unsigned char *name,
> int name_len, struct fat_slot_info *sinfo)
> @@ -1176,7 +1175,7 @@ static int fat_add_new_entries(struct inode *dir, void *slots, int nr_slots,
>
> /*
> * The minimum cluster size is 512bytes, and maximum entry
> - * size is 32*slots (672bytes). So, iff the cluster size is
> + * size is 32*slots (672bytes). So, if the cluster size is
iff is right here. iff == if and only if
> -// fat_cache_add(inode, new_fclus, new_dclus);
I guess this still worth to keep as FIXME. This meant the following.
/*
* FIXME: Although we can add this cache, fat_cache_add() is assuming to
* be called after liner search with fat_cache_id.
*/
> } else {
> MSDOS_I(inode)->i_start = new_dclus;
> MSDOS_I(inode)->i_logstart = new_dclus;
Other parts looks fine.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2012-12-19 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 16:50 Ravishankar N
2012-12-19 15:57 ` OGAWA Hirofumi [this message]
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=87ehimdogr.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=cyberax82@gmail.com \
--cc=linkinjeon@gmail.com \
--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 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®