From: Julien Grall <julien@xen.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Cc: tpearson@raptorengineering.com,
George Dunlap <george.dunlap@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Shawn Anastasio <shawnanastasio@raptorengineering.com>,
xen-devel@lists.xenproject.org,
Shawn Anastasio <shawn@anastas.io>
Subject: Re: [PATCH 2/3] xen/ppc: Implement early serial printk on PaPR/pseries
Date: Fri, 9 Jun 2023 10:46:22 +0100 [thread overview]
Message-ID: <1c35f696-5a65-06da-8af5-685b8ad2e849@xen.org> (raw)
In-Reply-To: <d52feaa7-4217-973e-19fe-9ec027eed5fc@citrix.com>
Hi Andrew,
On 09/06/2023 10:43, Andrew Cooper wrote:
> On 09/06/2023 10:38 am, Jan Beulich wrote:
>> On 09.06.2023 11:29, Andrew Cooper wrote:
>>> On 09/06/2023 10:22 am, Jan Beulich wrote:
>>>>> --- /dev/null
>>>>> +++ b/xen/arch/ppc/boot_of.c
>>>>> @@ -0,0 +1,122 @@
>>>>> +/* SPDX-License-Identifier: GPL-2.0-or-later */
>>>> By default we mean to use ...
>>>>
>>>>> --- /dev/null
>>>>> +++ b/xen/arch/ppc/early_printk.c
>>>>> @@ -0,0 +1,36 @@
>>>>> +/* SPDX-License-Identifier: GPL-2.0 */
>>>> ... the more modern form of this (GPL-2.0-only). Anything deviating from
>>>> that may want justifying in the description.
>>> GPL-2.0-or-later is fine.
>> Hmm, I was merely following
>> https://lists.xen.org/archives/html/xen-devel/2023-06/msg00415.html.
>> The text at the top of ./COPYING looks to suggest -only, and I'm
>> unaware of any other place where our default is actually written down.
>
> The license is chosen by the submitter/copyright holder, based on their
> preferences/wishes.
>
> It's fine for Xen to say "if you've got no vested interest, we recommend
> GPL-2.0-only", but that is strictly a recommendation and no more.
>
> If the submitter chooses GPL-2.0-or-later, that is their prerogative.
> We have plenty of GPL-2.0-or-later code in Xen.
From my past experience, the submitters tend to just copy the license
from an existing file in Xen rather than explicitly choosing it. So I
think it is fair to ask the question because our original and default
license is GPLv2 nor GPLv2+.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2023-06-09 9:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 15:06 [PATCH 0/3] Initial support for Power Shawn Anastasio
2023-06-07 15:06 ` [PATCH 1/3] xen: Add files needed for minimal Power build Shawn Anastasio
2023-06-09 9:15 ` Jan Beulich
2023-06-09 15:34 ` Shawn Anastasio
2023-06-07 15:06 ` [PATCH 2/3] xen/ppc: Implement early serial printk on PaPR/pseries Shawn Anastasio
2023-06-09 9:22 ` Jan Beulich
2023-06-09 9:29 ` Andrew Cooper
2023-06-09 9:38 ` Jan Beulich
2023-06-09 9:43 ` Julien Grall
2023-06-09 9:43 ` Andrew Cooper
2023-06-09 9:46 ` Julien Grall [this message]
2023-06-09 9:54 ` Andrew Cooper
2023-06-09 10:12 ` Julien Grall
2023-06-09 15:01 ` Shawn Anastasio
2023-06-09 16:07 ` Julien Grall
2023-06-09 16:20 ` Shawn Anastasio
2023-06-12 15:19 ` George Dunlap
2023-06-12 15:31 ` Julien Grall
2023-06-13 14:59 ` Shawn Anastasio
2023-06-09 15:36 ` Shawn Anastasio
2023-06-07 15:06 ` [PATCH 3/3] maintainers: Add PPC64 maintainer Shawn Anastasio
2023-06-09 9:04 ` Jan Beulich
2023-06-09 15:40 ` Shawn Anastasio
2023-06-07 18:07 ` [PATCH 0/3] Initial support for Power Andrew Cooper
2023-06-07 19:01 ` Shawn Anastasio
2023-06-07 19:30 ` Andrew Cooper
2023-06-08 15:19 ` Shawn Anastasio
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=1c35f696-5a65-06da-8af5-685b8ad2e849@xen.org \
--to=julien@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=shawn@anastas.io \
--cc=shawnanastasio@raptorengineering.com \
--cc=sstabellini@kernel.org \
--cc=tpearson@raptorengineering.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).