From: Pieter Smith <pieter@boesman.nl>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:FUSE: FILESYSTEM..."
<fuse-devel@lists.sourceforge.net>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v6 4/7] fs/fuse: support compiling out splice
Date: Sun, 7 Dec 2014 14:00:40 +0100 [thread overview]
Message-ID: <20141207130040.GA8267@smipidev> (raw)
In-Reply-To: <CAJfpegu+NQQ_+af=6UXi2=fyTJK1CsQBZ2++Nysu4mume4UEOQ@mail.gmail.com>
On Fri, Dec 05, 2014 at 11:44:36AM +0100, Miklos Szeredi wrote:
> On Thu, Dec 4, 2014 at 6:50 PM, Pieter Smith <pieter@boesman.nl> wrote:
> > To implement splice support, fs/fuse makes use of nosteal_pipe_buf_ops. This
> > struct is exported by fs/splice. The goal of the larger patch set is to
> > completely compile out fs/splice, so uses of the exported struct need to be
> > compiled out along with fs/splice.
> >
> > This patch therefore compiles out splice support in fs/fuse when
> > CONFIG_SYSCALL_SPLICE is undefined.
> >
> > Signed-off-by: Pieter Smith <pieter@boesman.nl>
>
>
> In the future could you PLEASE PLEASE cut the fuse-devel Cc from the
> non-fuse specific patches (and I guess that goes for any other
> subsystem specific lists and persons as well)?
>
> Otherwise:
>
> Acked-by: Miklos Szeredi <mszeredi@suse.cz>
>
> Thanks,
> Miklos
I added your Acked-by and removed you and fuse-dev from postings on future
versions of this patch-set.
Thanks,
Pieter
next prev parent reply other threads:[~2014-12-07 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 17:50 [PATCH v6 0/7] kernel tinification: optionally compile out splice family of syscalls (splice, vmsplice, tee and sendfile) Pieter Smith
2014-12-04 17:50 ` [PATCH v6 1/7] fs: move sendfile syscall into fs/splice Pieter Smith
2014-12-04 17:50 ` [PATCH v6 3/7] fs/splice: support compiling out splice-family syscalls Pieter Smith
2014-12-04 17:50 ` [PATCH v6 4/7] fs/fuse: support compiling out splice Pieter Smith
[not found] ` <1417715473-24110-5-git-send-email-pieter-qeJ+1H9vRZbz+pZb47iToQ@public.gmane.org>
2014-12-05 10:44 ` Miklos Szeredi
2014-12-07 13:00 ` Pieter Smith [this message]
[not found] ` <1417715473-24110-1-git-send-email-pieter-qeJ+1H9vRZbz+pZb47iToQ@public.gmane.org>
2014-12-04 17:50 ` [PATCH v6 2/7] fs: moved kernel_write to fs/read_write Pieter Smith
2014-12-04 17:50 ` [PATCH v6 5/7] net/core: support compiling out splice Pieter Smith
2014-12-04 17:50 ` [PATCH v6 6/7] fs/nfsd: " Pieter Smith
2014-12-04 17:50 ` [PATCH v6 7/7] fs/splice: full support for " Pieter Smith
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=20141207130040.GA8267@smipidev \
--to=pieter@boesman.nl \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).