From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <r.hieber@pengutronix.de>
Subject: [ptxdist] [PATCH v2 1/5] bluez: fix license string
Date: Mon, 12 Nov 2018 15:56:36 +0100 [thread overview]
Message-ID: <20181112145640.22901-2-r.hieber@pengutronix.de> (raw)
In-Reply-To: <20181112145640.22901-1-r.hieber@pengutronix.de>
Fixes: 02aff14f0d6a824609cbcc1410e45 "[bluez] version bump 3.36 -> 4.69"
Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
---
rules/bluez.make | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rules/bluez.make b/rules/bluez.make
index de6a1e5ec..246c7eab6 100644
--- a/rules/bluez.make
+++ b/rules/bluez.make
@@ -23,7 +23,7 @@ BLUEZ_SUFFIX := tar.gz
BLUEZ_URL := $(call ptx/mirror, KERNEL, bluetooth/$(BLUEZ).$(BLUEZ_SUFFIX))
BLUEZ_SOURCE := $(SRCDIR)/$(BLUEZ).$(BLUEZ_SUFFIX)
BLUEZ_DIR := $(BUILDDIR)/$(BLUEZ)
-BLUEZ_LICENSE := GPL-2.0-or-later LGPL-2.1-or-later
+BLUEZ_LICENSE := GPL-2.0-or-later AND LGPL-2.1-or-later
ifdef PTXCONF_BLUEZ_INSTALL_TESTSCRIPTS
BLUEZ_DEVPKG := NO
endif
--
2.19.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-11-12 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 14:56 [ptxdist] [PATCH v2 0/5] bluez fixes and version bump to 5.50 Roland Hieber
2018-11-12 14:56 ` Roland Hieber [this message]
2018-11-12 14:56 ` [ptxdist] [PATCH v2 2/5] bluez: consistently make use of $(ptx/nl) Roland Hieber
2018-11-12 14:56 ` [ptxdist] [PATCH v2 3/5] bluez: make it possible to disable building the tools Roland Hieber
2018-11-12 14:56 ` [ptxdist] [PATCH v2 4/5] bluez: rename PTXCONF_BLUEZ{_UTILS -> _TOOLS}* for consistency Roland Hieber
2018-11-12 14:56 ` [ptxdist] [PATCH v2 5/5] bluez: version bump 5.30 -> 5.50 Roland Hieber
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=20181112145640.22901-2-r.hieber@pengutronix.de \
--to=r.hieber@pengutronix.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