From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>, Roman Gushchin <guro@fb.com>,
YueHaibing <yuehaibing@huawei.com>, Yonghong Song <yhs@fb.com>,
Stanislav Fomichev <sdf@google.com>, Sean Young <sean@mess.org>,
Jiri Benc <jbenc@redhat.com>,
David Calavera <david.calavera@gmail.com>,
Andrey Ignatov <rdna@fb.com>, Joe Stringer <joe@wand.net.nz>,
David Ahern <dsahern@gmail.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Petar Penkov <ppenkov@stanford.edu>,
Sandipan Das <sandipan@linux.ibm.com>,
Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>,
Stephen Hemminger <stephen@networkplumber.org>,
John Fastabend <john.fastabend@gmail.com>,
Taeung Song <treeze.taeung@gmail.com>,
Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Quentin Monnet <quentin.monnet@netronome.com>,
okash.khawaja@gmail.com, netdev@vger.kernel.org
Subject: Re: [patch 8/9] tools: bpftool: Cleanup license mess
Date: Thu, 17 Jan 2019 15:24:30 -0800 [thread overview]
Message-ID: <20190117152430.7e47764e@cakuba.netronome.com> (raw)
In-Reply-To: <20190117231501.560475279@linutronix.de>
On Fri, 18 Jan 2019 00:14:24 +0100, Thomas Gleixner wrote:
> Precise and non-ambiguous license information is important. The recent
> relicensing of the bpftools introduced a license conflict.
>
> The files have now:
>
> SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause
>
> and
>
> * This program is free software; you can redistribute it and/or
> * modify it under the terms of the GNU General Public License
> * as published by the Free Software Foundation; either version
> * 2 of the License, or (at your option) any later version
>
> Amazingly about 20 people acked that change and neither they nor the
> committer noticed. Oh well.
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Sorry about that!
These files as you found out are from Stephen, so we probably don't
need the full litany of acks.
next prev parent reply other threads:[~2019-01-17 23:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 23:14 [patch 0/9] treewide: Cleanup recently added " Thomas Gleixner
2019-01-17 23:14 ` [patch 1/9] block: Cleanup license notice Thomas Gleixner
2019-01-18 2:53 ` Bart Van Assche
2019-01-18 4:21 ` Jens Axboe
2019-01-17 23:14 ` [patch 2/9] crypto: aegis - Cleanup license mess Thomas Gleixner
2019-01-18 8:02 ` Ondrej Mosnáček
2019-01-25 10:47 ` Herbert Xu
2019-01-17 23:14 ` [patch 3/9] crypto: morus " Thomas Gleixner
2019-01-18 0:26 ` Fabio Estevam
2019-01-18 6:50 ` Greg Kroah-Hartman
2019-01-18 8:00 ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 4/9] crypto: aegis - Convert to SPDX license identifiers Thomas Gleixner
2019-01-18 8:01 ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 5/9] crypto: morus " Thomas Gleixner
2019-01-18 8:02 ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 6/9] ceph: quota: Cleanup license mess Thomas Gleixner
2019-01-18 9:42 ` Luis Henriques
2019-01-18 10:48 ` Ilya Dryomov
2019-01-18 10:54 ` Thomas Gleixner
2019-01-17 23:14 ` [patch 7/9] smb3: " Thomas Gleixner
2019-01-19 5:43 ` Steve French
2019-01-17 23:14 ` [patch 8/9] tools: bpftool: " Thomas Gleixner
2019-01-17 23:24 ` Jakub Kicinski [this message]
2019-01-18 0:00 ` Thomas Gleixner
2019-01-18 23:28 ` Alexei Starovoitov
2019-01-17 23:14 ` [patch 9/9] vfio/pci: " Thomas Gleixner
2019-01-23 20:05 ` Alex Williamson
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=20190117152430.7e47764e@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bhole_prashant_q7@lab.ntt.co.jp \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=david.calavera@gmail.com \
--cc=dsahern@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=guro@fb.com \
--cc=jbenc@redhat.com \
--cc=joe@wand.net.nz \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=okash.khawaja@gmail.com \
--cc=ppenkov@stanford.edu \
--cc=quentin.monnet@netronome.com \
--cc=rdna@fb.com \
--cc=sandipan@linux.ibm.com \
--cc=sdf@google.com \
--cc=sean@mess.org \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=treeze.taeung@gmail.com \
--cc=yhs@fb.com \
--cc=yuehaibing@huawei.com \
/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
Powered by JetHome