All of lore.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, bfields@fieldses.org,
	viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
	Namjae Jeon <namjae.jeon@samsung.com>,
	Ravishankar N <ravi.n1@samsung.com>,
	Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [PATCH v4 3/4] fat (exportfs): rebuild directory-inode if fat_dget() fails
Date: Tue, 23 Oct 2012 16:53:05 +0900	[thread overview]
Message-ID: <873915k4ke.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd9Bv4Vv1sk0u9t0d3UubUy8DvTty=WNOFyDxwRuQh=CxA@mail.gmail.com> (Namjae Jeon's message of "Tue, 23 Oct 2012 16:34:39 +0900")

Namjae Jeon <linkinjeon@gmail.com> writes:

>>And this is doing same
>> thing with readdir, so we will have to clean this up as I said before.
> When I checked, I didn't understand about same thing readdir and this
> function yet. Because even though minor conditions match but
> functionality wise both are different.

Hm, I may not be understanding it correctly. I thought the both are
looking the key up? The key of readdir is the name, the key of this is
the logstart.

So, I thought it should be similar. However, I just may be wrong
somewhere... Well, even if those are possible to merge, it should be
separated patch though.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2012-10-23  7:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07  8:32 [PATCH v4 3/4] fat (exportfs): rebuild directory-inode if fat_dget() fails Namjae Jeon
2012-10-13  9:27 ` OGAWA Hirofumi
2012-10-13 14:03   ` Namjae Jeon
2012-10-13 14:35     ` OGAWA Hirofumi
2012-10-13 15:14       ` Namjae Jeon
2012-10-13 16:50         ` OGAWA Hirofumi
2012-10-15  7:28           ` Namjae Jeon
2012-10-15  7:57             ` OGAWA Hirofumi
2012-10-15 13:20               ` Namjae Jeon
2012-10-23  7:34   ` Namjae Jeon
2012-10-23  7:53     ` OGAWA Hirofumi [this message]
2012-10-23 11:38       ` Namjae Jeon

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=873915k4ke.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=a.sahrawat@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=linkinjeon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=ravi.n1@samsung.com \
    --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 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.