From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Hermann <christian.hermann@hytera.de>
Subject: Re: [ptxdist] [PATCH v3 6/9] pciutils: fix license identifier
Date: Fri, 12 Apr 2019 08:50:47 +0200 [thread overview]
Message-ID: <20190412065047.hrez6ycav3t7oqiy@pengutronix.de> (raw)
In-Reply-To: <20190405151209.31032-6-christian.hermann@hytera.de>
On Fri, Apr 05, 2019 at 05:12:06PM +0200, Christian Hermann wrote:
> Signed-off-by: Christian Hermann <christian.hermann@hytera.de>
> ---
> rules/pciutils.make | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/rules/pciutils.make b/rules/pciutils.make
> index 6ef7e14f7..be930fc60 100644
> --- a/rules/pciutils.make
> +++ b/rules/pciutils.make
> @@ -24,7 +24,7 @@ PCIUTILS_SUFFIX := tar.xz
> PCIUTILS_URL := $(call ptx/mirror, KERNEL, ../software/utils/pciutils/$(PCIUTILS).$(PCIUTILS_SUFFIX))
> PCIUTILS_SOURCE := $(SRCDIR)/$(PCIUTILS).$(PCIUTILS_SUFFIX)
> PCIUTILS_DIR := $(BUILDDIR)/$(PCIUTILS)
> -PCIUTILS_LICENSE := GPL-2.0-only
> +PCIUTILS_LICENSE := GPL-2.0-or-later
Where do you get the 'or later' from. I can only find "Can be freely
distributed and used under the terms of the GNU GPL." in the code and a
GPL-2.0 license text.
Michael
>
> # ----------------------------------------------------------------------------
> # Prepare
> --
> 2.21.0
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-04-12 6:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 15:12 [ptxdist] [PATCH v3 1/9] acl: " Christian Hermann
2019-04-05 15:12 ` [ptxdist] [PATCH v3 2/9] inetutils: add " Christian Hermann
2019-04-05 15:12 ` [ptxdist] [PATCH v3 3/9] nodejs: fix " Christian Hermann
2019-04-12 6:33 ` Michael Olbrich
2019-04-05 15:12 ` [ptxdist] [PATCH v3 4/9] ntp: " Christian Hermann
2019-04-12 6:42 ` Michael Olbrich
2019-04-05 15:12 ` [ptxdist] [PATCH v3 5/9] openldap: " Christian Hermann
2019-04-12 6:48 ` Michael Olbrich
2019-04-05 15:12 ` [ptxdist] [PATCH v3 6/9] pciutils: " Christian Hermann
2019-04-12 6:50 ` Michael Olbrich [this message]
[not found] ` <b891e040-65f7-0e5a-5f54-680996f94994@hytera.de>
2019-04-16 6:09 ` Michael Olbrich
2019-04-05 15:12 ` [ptxdist] [PATCH v3 7/9] perl: " Christian Hermann
2019-04-12 6:56 ` Michael Olbrich
2019-04-05 15:12 ` [ptxdist] [PATCH v3 8/9] tar: " Christian Hermann
2019-04-05 15:12 ` [ptxdist] [PATCH v3 9/9] tmux: " Christian Hermann
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=20190412065047.hrez6ycav3t7oqiy@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.hermann@hytera.de \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox