qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Marek Vasut <marex@denx.de>
Cc: Juro Bystricky <juro.bystricky@intel.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	jurobystricky@hotmail.com, Chris Wulff <crwulff@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/1] nios2: Add Altera JTAG UART emulation
Date: Wed, 8 Feb 2017 23:33:43 +0000	[thread overview]
Message-ID: <CAFEAcA-AaWtH8hqLVe+hr-FLAyusuiismw3safmR6mcxVnfLDg@mail.gmail.com> (raw)
In-Reply-To: <4c51c959-fe9c-b27f-552a-84d8a2fe68c1@denx.de>

On 8 February 2017 at 23:22, Marek Vasut <marex@denx.de> wrote:
> On 02/09/2017 12:06 AM, Juro Bystricky wrote:
>> + * 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.
>> + *
>> + * You should have received a copy of the GNU General Public License along
>> + * with this program; if not, see <http://www.gnu.org/licenses/>.
>
> Isn't QEMU GPLv2 only and NOT GPLv2+ ?

As a binary as a whole QEMU is GPLv2, because that is the most
restrictive and thus the controlling license. Individual
source files are under a variety of licenses, which is
fine as long as those licenses are GPL-2-compatible.
We have a preference against 2-only (see the LICENSE file),
and also you should at least use a license we're already
using. GPL2-or-later is fine and a common choice.

> btw for trivial patches like this, cover letter is not necessary .

The rough rule is "single patches don't need a cover letter;
series of more than one patch always do."

thanks
-- PMM

  reply	other threads:[~2017-02-08 23:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 23:06 [Qemu-devel] [PATCH v3 0/1] nios2: Add Altera JTAG UART emulation Juro Bystricky
2017-02-08 23:06 ` [Qemu-devel] [PATCH v3 1/1] " Juro Bystricky
2017-02-08 23:22   ` Marek Vasut
2017-02-08 23:33     ` Peter Maydell [this message]
2017-02-09  0:54     ` Bystricky, Juro
2017-02-09  8:46       ` Marek Vasut
2017-02-09 15:22         ` Bystricky, Juro
2017-02-09 15:37           ` Marek Vasut
2017-02-09 16:07             ` Bystricky, Juro
2017-02-09 16:13               ` Marek Vasut
2017-02-09 16:34                 ` Bystricky, Juro
2017-02-09 17:25                   ` Marek Vasut

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=CAFEAcA-AaWtH8hqLVe+hr-FLAyusuiismw3safmR6mcxVnfLDg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=crwulff@gmail.com \
    --cc=juro.bystricky@intel.com \
    --cc=jurobystricky@hotmail.com \
    --cc=marex@denx.de \
    --cc=qemu-devel@nongnu.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).