From: Jonathan Corbet <corbet@lwn.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: clarify other licenses in LICENSES/
Date: Fri, 3 May 2019 06:34:53 -0600 [thread overview]
Message-ID: <20190503063453.1378ff99@lwn.net> (raw)
In-Reply-To: <20190430114134.GA17027@kroah.com>
On Tue, 30 Apr 2019 13:41:34 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Tue, Apr 30, 2019 at 06:51:27AM -0400, Christoph Hellwig wrote:
> > Hi all,
> >
> > this series splits the others category into dual or deprecated,
> > and also fixes up some other minor bits in the documentation for
> > these non-preferred licenses.
>
> Looks good to me, thanks for doing this!
>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
I've applied the set, thanks.
jon
prev parent reply other threads:[~2019-05-03 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 10:51 clarify other licenses in LICENSES/ Christoph Hellwig
2019-04-30 10:51 ` [PATCH 1/3] docs: Don't reference the ZLib license in license-rules.rst Christoph Hellwig
2019-04-30 10:51 ` [PATCH 2/3] LICENSES: Clearly mark dual license only licenses Christoph Hellwig
2019-04-30 10:51 ` [PATCH 3/3] LICENSES: Rename other to deprecated Christoph Hellwig
2019-05-14 10:26 ` Borislav Petkov
2019-05-14 13:49 ` Christoph Hellwig
2019-05-14 14:10 ` Borislav Petkov
2019-04-30 11:41 ` clarify other licenses in LICENSES/ Greg Kroah-Hartman
2019-05-03 12:34 ` Jonathan Corbet [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=20190503063453.1378ff99@lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.