linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Peter Krystad <pkrystad@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3 bluez 2/2] Add A2MP definitions
Date: Mon, 12 Dec 2011 12:42:57 +0200	[thread overview]
Message-ID: <20111212104257.GA12316@x220> (raw)
In-Reply-To: <1320280606-32677-3-git-send-email-pkrystad@codeaurora.org>

Hi Peter,

On Wed, Nov 02, 2011, Peter Krystad wrote:
> + *	This program is free software; you can redistribute it and/or modify
> + *	it under the terms of the GNU General Public License version 2 and
> + *	only version 2 as published by the Free Software Foundation.

I'm still waiting for an update from you on this licensing detail issue.
As Marcel said we'd like to keep the license terms of all libbluetooth
(and also bluez user-space for that matter) consistent. Since you're
already contributing code under "GPL v2 or later" (for the existing .c
and .h files) would it be possible for you to use that for all parts of
your patches?

Johan

  reply	other threads:[~2011-12-12 10:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03  0:36 [PATCH v3 bluez 0/2] Add BT 3.0+HS definitions Peter Krystad
2011-11-03  0:36 ` [PATCH v3 bluez 1/2] Add L2CAP Create/Move Channel definitions Peter Krystad
2011-11-03  0:36 ` [PATCH v3 bluez 2/2] Add A2MP definitions Peter Krystad
2011-12-12 10:42   ` Johan Hedberg [this message]
2011-12-12 12:28     ` Andrei Emeltchenko
2011-12-13  1:01     ` Peter Krystad
  -- strict thread matches above, loose matches on Subject: below --
2011-11-17  4:25 Peter Krystad
2011-11-17  9:26 ` Johan Hedberg
2011-11-17 18:19   ` Peter Krystad
2011-11-18  5:15   ` Marcel Holtmann
2011-11-17  9:45 ` Andrei Emeltchenko
2011-11-17 19:05   ` Peter Krystad

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=20111212104257.GA12316@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pkrystad@codeaurora.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;
as well as URLs for NNTP newsgroup(s).