linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH] vfs: export lseek_execute() to modules
Date: Mon, 24 Jun 2013 05:55:13 -0700	[thread overview]
Message-ID: <20130624125513.GA7921@infradead.org> (raw)
In-Reply-To: <51C832F8.2090707@oracle.com>

On Mon, Jun 24, 2013 at 07:52:24PM +0800, Jeff Liu wrote:
> From: Jie Liu <jeff.liu@oracle.com>
> 
> For those file systems(btrfs/ext4/xfs/ocfs2/tmpfs) that support
> SEEK_DATA/SEEK_HOLE functions, we end up handling the similar
> matter in lseek_execute() to verify the final offset.
> 
> To reduce the duplications, this patch make lseek_execute() public
> accessible so that we can call it directly from them.
> 
> Thanks Dave Chinner for this suggestion.

Please add a kerneldoc comment explaining the use of this function.


  reply	other threads:[~2013-06-24 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 11:52 [RFC PATCH] vfs: export lseek_execute() to modules Jeff Liu
2013-06-24 12:55 ` Christoph Hellwig [this message]
2013-06-25  2:30   ` Jeff Liu

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=20130624125513.GA7921@infradead.org \
    --to=hch@infradead.org \
    --cc=jeff.liu@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.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).