From: Simon Horman <simon.horman@corigine.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 00/10] SPDX cleanups
Date: Fri, 13 Jan 2023 11:36:05 +0100 [thread overview]
Message-ID: <Y8E0Fej++QpZaUDb@corigine.com> (raw)
In-Reply-To: <20230111031712.19037-1-stephen@networkplumber.org>
On Tue, Jan 10, 2023 at 07:17:02PM -0800, Stephen Hemminger wrote:
> Cleanout the GPL boiler plate in iproute.
> Better to use modern SPDX to document the license
> rather than copy/paste same text in multiple places.
>
> There is no change in licensing here, and none is planned.
Hi Stephen,
FWIIW, this series looks good to me, modulo a minor comment
on patch 09/10 which I am happy for you to ignore.
Reviewed-by: Simon Horman <simon.horman@corigine.com>
prev parent reply other threads:[~2023-01-13 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 3:17 [PATCH iproute2 00/10] SPDX cleanups Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 01/10] bridge: use SPDX Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 02/10] genl: " Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 03/10] lib: replace GPL boilerplate with SPDX Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 04/10] devlink: use SPDX Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 05/10] ip: " Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 06/10] testsuite: " Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 07/10] tipc: " Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 08/10] tc: replace GPL-BSD boilerplate in codel and fq Stephen Hemminger
2023-01-11 3:17 ` [PATCH iproute2 09/10] tc: use SPDX Stephen Hemminger
2023-01-13 10:34 ` Simon Horman
2023-01-13 17:32 ` Stephen Hemminger
2023-01-14 15:42 ` Simon Horman
2023-01-11 3:17 ` [PATCH iproute2 10/10] misc: " Stephen Hemminger
2023-01-13 10:36 ` Simon Horman [this message]
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=Y8E0Fej++QpZaUDb@corigine.com \
--to=simon.horman@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).