From: Jeff Garzik <jeff@garzik.org>
To: Jens Axboe <axboe@suse.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] splice exports
Date: Fri, 31 Mar 2006 18:14:56 -0500 [thread overview]
Message-ID: <442DB7F0.8090000@garzik.org> (raw)
In-Reply-To: <20060331183617.GD14022@suse.de>
Jens Axboe wrote:
> On Fri, Mar 31 2006, Jeff Garzik wrote:
>> Jens Axboe wrote:
>>> On Fri, Mar 31 2006, Arjan van de Ven wrote:
>>>> On Thu, 2006-03-30 at 23:06 -0500, Jeff Garzik wrote:
>>>>> Woe be unto he who builds their filesystems as modules.
>>>> since splice support is highly linux specific and new.. shouldn't these
>>>> be _GPL exports?
>>> Yes they should, I'll add that to the current splice tree.
>> Why? We don't usually restrict filesystems in such ways... I would
>> rather a binary-only module reference generic_file_splice_read() than
>> create its own.
>
> You could use that very same argument for any piece of the kernel, then,
> so I don't think that adds much value to _not_ exporting it GPL.
Not really, because I'm considering the Real World(tm) users, not
abstract theory :) The other filesystem junk is exported non-GPL, and
existing binary-only filesystems use that stuff.
IOW its a bit rude to say "oh you can have your BO filesystem, just not
splice support."
Jeff
next prev parent reply other threads:[~2006-03-31 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 4:06 [PATCH] splice exports Jeff Garzik
2006-03-31 7:17 ` Jens Axboe
2006-03-31 11:01 ` Arjan van de Ven
2006-03-31 11:02 ` Jens Axboe
2006-03-31 14:00 ` Jeff Garzik
2006-03-31 18:36 ` Jens Axboe
2006-03-31 23:14 ` Jeff Garzik [this message]
2006-04-01 1:33 ` Arjan van de Ven
2006-04-02 18:02 ` Jens Axboe
2006-03-31 13:28 ` Sam Ravnborg
2006-03-31 13:31 ` Jens Axboe
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=442DB7F0.8090000@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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.