From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Benny Halevy <bhalevy@panasas.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] EXPORT_SYMBOL(d_obtain_alias) rather than EXPORT_SYMBOL_GPL
Date: Tue, 24 Feb 2009 13:36:33 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0902241335010.3111@localhost.localdomain> (raw)
In-Reply-To: <20090224213222.GH28946@ZenIV.linux.org.uk>
On Tue, 24 Feb 2009, Al Viro wrote:
>
> As an aside, EXPORT_SYMBOL_GPL() is obnoxious shite anyway. If
> something is not a safe API, exporting it to default-quality 3rd-party
> code is bad and while GPL might be many things, it is not a magical
> "teach average programmer to find his arse without a map" pill.
Actually, I have had lawyers tell me it's actually a good idea, and shows
"intent". Intent may not matter for code in the sense that the code does
what the code does regardless of what the programmer _intended_ it to do,
but it does matter in legal terms.
So don't think of it in technical terms. It's not about good quality or
about finding your arse without maps.
Linus
prev parent reply other threads:[~2009-02-24 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 7:13 Ping: d_obtain_alias Benny Halevy
2009-02-21 17:40 ` Christoph Hellwig
2009-02-21 8:41 ` Benny Halevy
2009-02-21 19:40 ` Andrew Morton
2009-02-21 19:49 ` Linus Torvalds
2009-02-24 20:11 ` [PATCH] EXPORT_SYMBOL(d_obtain_alias) rather than EXPORT_SYMBOL_GPL Benny Halevy
2009-02-24 21:32 ` Al Viro
2009-02-24 21:36 ` Linus Torvalds [this message]
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=alpine.LFD.2.00.0902241335010.3111@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@ZenIV.linux.org.uk \
/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