From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, gnomes@lxorguk.ukuu.org.uk,
gregkh@linuxfoundation.org, jkosina@suse.cz, bhelgaas@google.com,
linux-pci@vger.kernel.org, xen-devel@lists.xenproject.org,
bp@suse.de
Subject: Re: [PATCH] Documentation: extend use case for EXPORT_SYMBOL_GPL()
Date: Thu, 28 May 2015 21:18:44 +0200 [thread overview]
Message-ID: <20150528191844.GU23057@wotan.suse.de> (raw)
In-Reply-To: <20150528130923.42f34540@lwn.net>
On Thu, May 28, 2015 at 01:09:23PM -0600, Jonathan Corbet wrote:
> On Thu, 28 May 2015 11:56:01 -0700
> "Luis R. Rodriguez" <mcgrof@do-not-panic.com> wrote:
>
> > + Some maintainers and developers may however have a preference to
> > + require EXPORT_SYMBOL_GPL() when adding any new APIs or functionality.
>
> As a nit, I would take out "have a preference to".
Fine by me, do you need a new submission on my part of can you amend yourself?
> From what I can tell, there are developers who think this position makes
> little sense and, perhaps, risks diluting the value of EXPORT_SYMBOL_GPL()
> by attaching it to everything. My inclination, though, would be to accept
> this change as documentation of clear existing practice; whether that
> practice should change is, I think, a separate discussion.
Great, thanks.
Luis
next prev parent reply other threads:[~2015-05-28 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 18:56 [PATCH] Documentation: extend use case for EXPORT_SYMBOL_GPL() Luis R. Rodriguez
2015-05-28 19:09 ` Jonathan Corbet
2015-05-28 19:18 ` Luis R. Rodriguez [this message]
2015-05-28 19:35 ` Jonathan Corbet
2015-05-28 20:07 ` Al Viro
2015-05-28 21:17 ` Luis R. Rodriguez
2015-05-28 21:56 ` Al Viro
2015-05-28 23:10 ` Luis R. Rodriguez
2015-05-29 5:00 ` Christoph Hellwig
2015-05-29 17:40 ` Luis R. Rodriguez
2015-05-29 1:30 ` Rob Landley
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=20150528191844.GU23057@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mingo@elte.hu \
--cc=xen-devel@lists.xenproject.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