Skip to content

fstests: SPDX license conversion round 2

Dave Chinner fstests 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest6 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6dmapi: spdx license conversiondmapi/Makefile dmapi/src/Makefile dmapi/src/common/Makefile +86 more+89 -11790 replies
2/6include/: spdx license conversioninclude/Makefile include/builddefs.in include/buildmacros +12 more+15 -1340 replies
3/6lib/: spdx license conversionlib/Makefile lib/dataascii.c lib/databin.c +11 more+16 -1760 replies
4/6src/aio-dio-regress/: spdx license conversionsrc/aio-dio-regress/Makefile src/aio-dio-regress/aio-dio-append-write-read-race.c src/aio-dio-regress/aio-dio-cow-race.c +12 more+53 -2400 replies
5/6src/: spdx license conversionsrc/Makefile src/af_unix.c src/alloc.c +69 more+98 -8430 replies
6/6ltp/: spdx license conversionltp/Makefile ltp/aio-stress.c ltp/doio.c +4 more+10 -870 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/6] fstests: SPDX license conversion round 2

Hi folks,

This is a smaller set of patches that convert the remaining GPLv2 license templates in the fstests tree to SPDX tags. The patches should all be small enough to make it through to the list this time.

Mostly it was straight forward conversions with a little bit of manual cleanup, but there's a couple of things we need clarification on:

- src/log-writes has no copyright or license statements in either the code or in the upstream repository, so I haven't tagged it.

- src/perf has not copyright or license statements, but fstests is the upstream repository so I've tagged them as GPLv2.0

In both cases, we need Josef to add the correct copyrights and SPDX tags to these files, and in future we should not accept code that does not have either copyright or license statements in them.

There are some remaining files without tags. There are various different reasons for that - not GPLv2, license statement didn't match the scripts, no license statement to begin with, etc. These will be addressed in a future patch set.

Comments?

-Dave.