From: Christoph Hellwig <hch@infradead.org>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Separate out common fstatat code into vfs_fstatat
Date: Wed, 8 Apr 2009 16:32:09 -0400 [thread overview]
Message-ID: <20090408203209.GA14342@infradead.org> (raw)
In-Reply-To: <20090408160541.GA1812319@fiona.linuxhacker.ru>
On Wed, Apr 08, 2009 at 08:05:42PM +0400, Oleg Drokin wrote:
> This is a version incorporating Christoph's suggestion.
>
> Separate out common *fstatat functionality into a single function
> instead of duplicating it all over the code.
Looks good to me.
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2009-04-08 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 16:05 [PATCH] Separate out common fstatat code into vfs_fstatat Oleg Drokin
2009-04-08 20:32 ` Christoph Hellwig [this message]
2009-04-08 20:34 ` [PATCH] kill vfs_stat_fd / vfs_lstat_fd Christoph Hellwig
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=20090408203209.GA14342@infradead.org \
--to=hch@infradead.org \
--cc=green@linuxhacker.ru \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).