From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: huth@tuxfamily.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 36/36] next-cube: replace boiler-plate GPL 2.0 or later license text with SPDX identifier
Date: Wed, 23 Oct 2024 10:30:41 +0100 [thread overview]
Message-ID: <ZxjCQQjnJMPqBWt4@redhat.com> (raw)
In-Reply-To: <20241023085852.1061031-37-mark.cave-ayland@ilande.co.uk>
On Wed, Oct 23, 2024 at 09:58:52AM +0100, Mark Cave-Ayland wrote:
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> ---
> hw/m68k/next-cube.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/hw/m68k/next-cube.c b/hw/m68k/next-cube.c
> index eefb372dca..c961d5fef6 100644
> --- a/hw/m68k/next-cube.c
> +++ b/hw/m68k/next-cube.c
> @@ -4,10 +4,7 @@
> * Copyright (c) 2011 Bryce Lanham
> * Copyright (c) 2024 Mark Cave-Ayland
> *
> - * This code 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.
> + * SPDX-License-Identifier: GPL-2.0-or-later
Although the Kernel folks did such replacements, IMHO we should be
wary about removing existing license boilerplate text, as it is
potentially in conflict with the requirements in clause 1 of the
license to keep all existing notices intact, depending on your
interpretation.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-10-23 9:31 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 8:58 [PATCH 00/36] next-cube: more tidy-ups and improvements Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 01/36] next-cube: fix up compilation when DEBUG_NEXT is enabled Mark Cave-Ayland
2024-10-26 6:30 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 02/36] next-cube: remove 0x14020 dummy value from next_mmio_read() Mark Cave-Ayland
2024-10-26 7:44 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 03/36] next-cube: remove overlap between next.dma and next.mmio memory regions Mark Cave-Ayland
2024-10-24 2:42 ` Philippe Mathieu-Daudé
2024-10-24 8:31 ` Mark Cave-Ayland
2024-10-26 7:56 ` Thomas Huth
2024-10-26 21:13 ` Mark Cave-Ayland
2024-10-27 11:24 ` Thomas Huth
2024-10-28 22:06 ` Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 04/36] next-cube: remove cpu parameter from next_scsi_init() Mark Cave-Ayland
2024-10-26 7:59 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 05/36] next-cube: create new next.scsi container memory region Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 06/36] next-cube: move next_scsi_init() to next_pc_realize() Mark Cave-Ayland
2024-10-27 10:07 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 07/36] next-cube: introduce next_pc_init() object init function Mark Cave-Ayland
2024-10-27 10:25 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 08/36] next-cube: introduce next-scsi device Mark Cave-Ayland
2024-10-27 11:58 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 09/36] next-cube: move SCSI CSRs from next-pc to the " Mark Cave-Ayland
2024-10-28 16:21 ` Thomas Huth
2024-10-28 22:21 ` Mark Cave-Ayland
2024-11-01 16:37 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 10/36] next-cube: move SCSI 4020 logic from next-pc device to " Mark Cave-Ayland
2024-10-28 16:22 ` Thomas Huth
2024-10-28 22:23 ` Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 11/36] next-cube: move floppy disk MMIO to separate memory region in next-pc Mark Cave-Ayland
2024-10-28 16:31 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 12/36] next-cube: map ESCC registers as a subregion of the next.scr memory region Mark Cave-Ayland
2024-10-28 16:36 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 13/36] next-cube: move ESCC to be QOM child of next-pc device Mark Cave-Ayland
2024-10-28 16:39 ` Thomas Huth
2024-10-28 22:28 ` Mark Cave-Ayland
2024-11-01 16:34 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 14/36] next-cube: move timer MMIO to separate memory region on " Mark Cave-Ayland
2024-11-01 16:46 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 15/36] next-cube: move en ethernet " Mark Cave-Ayland
2024-11-02 7:26 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 16/36] next-cube: add empty slots for unknown accesses to next.scr memory region Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 17/36] next-cube: remove unused " Mark Cave-Ayland
2024-11-02 9:40 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 18/36] next-cube: rearrange NeXTState declarations to improve readability Mark Cave-Ayland
2024-11-02 9:41 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 19/36] next-cube: convert next-pc device to use Resettable interface Mark Cave-Ayland
2024-11-02 9:48 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 20/36] next-cube: rename typedef struct NextRtc to NeXTRTC Mark Cave-Ayland
2024-11-02 9:49 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 21/36] next-cube: use qemu_irq to drive int_status in next_scr2_rtc_update() Mark Cave-Ayland
2024-11-03 18:31 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 22/36] next-cube: separate rtc read and write shift logic Mark Cave-Ayland
2024-11-03 18:52 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 23/36] next-cube: always use retval to return rtc read values Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 24/36] next-cube: use named gpio to set RTC data bit in scr2 Mark Cave-Ayland
2024-11-09 7:51 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 25/36] next-cube: use named gpio to read " Mark Cave-Ayland
2024-11-09 7:55 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 26/36] next-cube: don't use rtc phase value of -1 Mark Cave-Ayland
2024-10-23 10:37 ` BALATON Zoltan
2024-10-24 8:28 ` Mark Cave-Ayland
2024-11-09 7:57 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 27/36] next-cube: QOMify NeXTRTC Mark Cave-Ayland
2024-10-24 2:44 ` Philippe Mathieu-Daudé
2024-10-24 8:41 ` Mark Cave-Ayland
2024-11-09 8:14 ` Thomas Huth
2024-11-11 21:30 ` Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 28/36] next-cube: move reset of next-rtc fields from next-pc to next-rtc Mark Cave-Ayland
2024-11-09 8:19 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 29/36] next-cube: move rtc-data-in gpio from next-pc to next-rtc device Mark Cave-Ayland
2024-11-09 8:21 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 30/36] next-cube: use named gpio output for next-rtc data Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 31/36] next-cube: add rtc-cmd-reset named gpio to reset the rtc state machine Mark Cave-Ayland
2024-11-09 8:24 ` Thomas Huth
2024-11-11 21:37 ` Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 32/36] next-cube: add rtc-power-out " Mark Cave-Ayland
2024-10-24 8:45 ` Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 33/36] next-cube: move next_rtc_cmd_is_write() and next_rtc_data_in_irq() functions Mark Cave-Ayland
2024-11-09 8:25 ` Thomas Huth
2024-11-11 21:39 ` Mark Cave-Ayland
2024-10-23 8:58 ` [PATCH 34/36] next-cube: rename old_scr2 and scr2_2 in next_scr2_rtc_update() Mark Cave-Ayland
2024-11-09 8:25 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 35/36] next-cube: add my copyright to the top of the file Mark Cave-Ayland
2024-11-09 8:26 ` Thomas Huth
2024-10-23 8:58 ` [PATCH 36/36] next-cube: replace boiler-plate GPL 2.0 or later license text with SPDX identifier Mark Cave-Ayland
2024-10-23 9:30 ` Daniel P. Berrangé [this message]
2024-10-23 9:42 ` Mark Cave-Ayland
2024-10-29 11:22 ` [PATCH 00/36] next-cube: more tidy-ups and improvements Peter Maydell
2024-10-29 12:51 ` Mark Cave-Ayland
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=ZxjCQQjnJMPqBWt4@redhat.com \
--to=berrange@redhat.com \
--cc=huth@tuxfamily.org \
--cc=mark.cave-ayland@ilande.co.uk \
--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).