linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, viro@zeniv.linux.org.uk, jmorris@namei.org,
	npiggin@suse.de, zohar@us.ibm.com, jack@suse.cz,
	jmalicki@metacarta.com, dsmith@redhat.com, serue@us.ibm.com,
	hch@lst.de, john@johnmccutchan.com, rlove@rlove.org,
	ebiederm@xmission.com, heiko.carstens@de.ibm.com,
	penguin-kernel@I-love.SAKURA.ne.jp, mszeredi@suse.cz,
	akpm@linux-foundation.org, matthew@wil.cx,
	hugh.dickins@tiscali.co.uk, kamezawa.hiroyu@jp.fujitsu.com,
	nishimura@mxp.nes.nec.co.jp, davem@davemloft.net, arnd@arndb.de,
	eric.dumazet@gmail.com
Subject: Re: [RFC PATCH 2/6] pipes: use alloc-file instead of duplicating code
Date: Fri, 4 Dec 2009 15:22:50 +0100	[thread overview]
Message-ID: <20091204142250.GF8742@kernel.dk> (raw)
In-Reply-To: <20091203195902.8925.2985.stgit@paris.rdu.redhat.com>

On Thu, Dec 03 2009, Eric Paris wrote:
> The pipe code duplicates the functionality of alloc-file and init-file.  Use
> the generic vfs functions instead of duplicating code.
> 
> Signed-off-by: Eric Paris <eparis@redhat.com>

Acked-by: Jens Axboe <jens.axboe@oracle.com>

-- 
Jens Axboe


  parent reply	other threads:[~2009-12-04 14:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 19:58 [RFC PATCH 1/6] shmem: use alloc_file instead of init_file Eric Paris
2009-12-03 19:59 ` [RFC PATCH 2/6] pipes: use alloc-file instead of duplicating code Eric Paris
2009-12-04  6:08   ` Miklos Szeredi
2009-12-04 18:54     ` Eric Paris
2009-12-04 14:22   ` Jens Axboe [this message]
2009-12-03 19:59 ` [RFC PATCH 3/6] inotify: use alloc_file instead of doing it internally Eric Paris
2009-12-04  6:58   ` Miklos Szeredi
2009-12-03 19:59 ` [RFC PATCH 4/6] networking: rework socket to fd mapping using alloc-file Eric Paris
2009-12-03 22:00   ` David Miller
2009-12-03 23:24     ` Eric Paris
2009-12-04  7:09   ` Miklos Szeredi
2009-12-03 19:59 ` [RFC PATCH 5/6] vfs: make init-file static Eric Paris
2009-12-03 22:44   ` Serge E. Hallyn
2009-12-04  4:04     ` Nick Piggin
2009-12-03 19:59 ` [RFC PATCH 6/6] fs: move get_empty_filp() deffinition to internal.h Eric Paris
2009-12-04  7:12   ` Miklos Szeredi
2009-12-04  5:58 ` [RFC PATCH 1/6] shmem: use alloc_file instead of init_file Miklos Szeredi
2009-12-04 14:19   ` Eric Paris
2009-12-04 15:35 ` Serge E. Hallyn

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=20091204142250.GF8742@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=dsmith@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=eparis@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=hch@lst.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=jack@suse.cz \
    --cc=jmalicki@metacarta.com \
    --cc=jmorris@namei.org \
    --cc=john@johnmccutchan.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew@wil.cx \
    --cc=mszeredi@suse.cz \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=npiggin@suse.de \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rlove@rlove.org \
    --cc=serue@us.ibm.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zohar@us.ibm.com \
    /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).