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



On 03/08/2017 01:50 AM, Greg Kroah-Hartman wrote:
> On Wed, Mar 08, 2017 at 01:25:49AM -0800, john.hubbard@gmail.com wrote:
>> From: John Hubbard <jhubbard@nvidia.com>
>>
>> Originally, kref_get and kref_put were available as
>> standard routines that even non-GPL device drivers
>> could use.
>
> As I stated in my response to the 0/1 of this patch, this sentence is
> not true, sorry, the inlined functions were GPL-v2-only.

OK, got it. I overlooked that point.

thanks
John Hubbard
NVIDIA

>
> thanks,
>
> greg k-h
>

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  9:25 [PATCH 0/1] refcount: restore kref_get and kref_put to non-GPL status john.hubbard
2017-03-08  9:25 ` [PATCH] " john.hubbard
2017-03-08  9:50   ` Greg Kroah-Hartman
2017-03-08  9:53     ` John Hubbard [this message]
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=de2e08c1-5bb3-e62a-a624-d2db2a54e6cc@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.hubbard@gmail.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