public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john.hubbard@gmail.com
To: Peter Zijlstra <peterz@infradead.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH 0/1] refcount: restore kref_get and kref_put to non-GPL status
Date: Wed,  8 Mar 2017 01:25:48 -0800	[thread overview]
Message-ID: <20170308092549.28982-1-jhubbard@nvidia.com> (raw)

From: John Hubbard <jhubbard@nvidia.com>

Hi,

Say, I'm 99% sure that this was just an oversight, so
I'm sticking my neck out here and floating a patch to
Put Things Back. I'm hoping that there is not some
firm reason to GPL-protect the basic kref_get and
kref_put routines, because when designing some
recent new (open-source, yay!) device drivers, we relied
on this being available, even for MIT-licensed code.


John Hubbard (1):
  refcount: restore kref_get and kref_put to non-GPL status

 lib/refcount.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.12.0

             reply	other threads:[~2017-03-08  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  9:25 john.hubbard [this message]
2017-03-08  9:25 ` [PATCH] refcount: restore kref_get and kref_put to non-GPL status john.hubbard
2017-03-08  9:50   ` Greg Kroah-Hartman
2017-03-08  9:53     ` John Hubbard
2017-03-08 16:03   ` Christoph Hellwig
2017-03-08  9:48 ` [PATCH 0/1] " Greg Kroah-Hartman
2017-03-08  9:59   ` John Hubbard
2017-03-08 10:12     ` Greg Kroah-Hartman
2017-03-08 10:52       ` John Hubbard

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=20170308092549.28982-1-jhubbard@nvidia.com \
    --to=john.hubbard@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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