public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] splice exports
Date: Sun, 2 Apr 2006 20:02:16 +0200	[thread overview]
Message-ID: <20060402180216.GD14022@suse.de> (raw)
In-Reply-To: <1143855184.3076.0.camel@laptopd505.fenrus.org>

On Sat, Apr 01 2006, Arjan van de Ven wrote:
> On Fri, 2006-03-31 at 18:14 -0500, Jeff Garzik wrote:
> > 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."
> 
> 
> it's a bit like saying "you can use all the standard unix interfaces,
> but these are very linux specific"; eg the same arguments for making lsm
> and other pieces _GPL; they're so linux specific that users that use
> these do so with linux in mind etc

Linus seems to agree with the _GPL not being appropriate as well, so I
guess I'll bow to the majority. This time :-)

-- 
Jens Axboe


  reply	other threads:[~2006-04-02 18:02 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
2006-04-01  1:33           ` Arjan van de Ven
2006-04-02 18:02             ` Jens Axboe [this message]
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=20060402180216.GD14022@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=jeff@garzik.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox