u-boot.git/tools/patman/test.py, branch master

patman: Rename test.py to test_checkpatch.py

2020-07-10T00:57:22+00:00

These tests check checkpatch.pl operation and can server as our tests for
the U-Boot-specific updates to that script. Rename the file and update
comments to indicate this.

Signed-off-by: Simon Glass

patman: Move to absolute imports

2020-04-26T20:25:21+00:00

At present patman sets the python path on startup so that it can access
the libraries it needs. If we convert to use absolute imports this is not
necessary.

Move patman to use absolute imports. This requires changes in tools which
use the patman libraries (which is most of them).

Signed-off-by: Simon Glass

patman: Use unicode for file I/O

2019-11-05T01:15:32+00:00

At present patman test fail in some environments which don't use utf-8
as the default file encoding. Add this explicitly.

Signed-off-by: Simon Glass

patman: Use the Change-Id, version, and prefix in the Message-Id

2019-10-15T14:40:03+00:00

As per the centithread on ksummit-discuss [1], there are folks who
feel that if a Change-Id is present in a developer's local commit that
said Change-Id could be interesting to include in upstream posts.
Specifically if two commits are posted with the same Change-Id there's
a reasonable chance that they are either the same commit or a newer
version of the same commit.  Specifically this is because that's how
gerrit has trained people to work.

There is much angst about Change-Id in upstream Linux, but one thing
that seems safe and non-controversial is to include the Change-Id as
part of the string of crud that makes up a Message-Id.

Let's give that a try.

In theory (if there is enough adoption) this could help a tool more
reliably find various versions of a commit.  This actually might work
pretty well for U-Boot where (I believe) quite a number of developers
use patman, so there could be critical mass (assuming that enough of
these people also use a git hook that adds Change-Id to their
commits).  I was able to find this git hook by searching for "gerrit
change id git hook" in my favorite search engine.

In theory one could imagine something like this could be integrated
into other tools, possibly even git-send-email.  Getting it into
patman seems like a sane first step, though.

NOTE: this patch is being posted using a patman containing this patch,
so you should be able to see the Message-Id of this patch and see that
it contains my local Change-Id, which ends in 2b9 if you want to
check.

[1] https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2019-August/006739.html

Signed-off-by: Douglas Anderson

patman: add test for SPDX license

2018-06-23T14:03:43+00:00

Add a test to exercise the check for a valid SPDX license.

Signed-off-by: Chris Packham 
Reviewed-by: Simon Glass

patman: Fix unit tests for SPDX

2018-06-07T19:25:03+00:00

The format of this line has changed. Update the patman test to suit.

Signed-off-by: Simon Glass 
Tested-by: Alex Kiernan

SPDX: Convert all of our single license tags to Linux Kernel style

2018-05-07T13:34:12+00:00

When U-Boot started using SPDX tags we were among the early adopters and
there weren't a lot of other examples to borrow from.  So we picked the
area of the file that usually had a full license text and replaced it
with an appropriate SPDX-License-Identifier: entry.  Since then, the
Linux Kernel has adopted SPDX tags and they place it as the very first
line in a file (except where shebangs are used, then it's second line)
and with slightly different comment styles than us.

In part due to community overlap, in part due to better tag visibility
and in part for other minor reasons, switch over to that style.

This commit changes all instances where we have a single declared
license in the tag as both the before and after are identical in tag
contents.  There's also a few places where I found we did not have a tag
and have introduced one.

Signed-off-by: Tom Rini

patman: Fix up tests to pass with newest checkpatch

2017-11-23T01:05:38+00:00

The checkpatch tool was updated but the patman tests were not. Fix this.

Signed-off-by: Simon Glass

patman: Add unicode to test patches

2017-06-09T02:21:59+00:00

Add some unicode to the test patches to make sure that patman does the
right thing.

Signed-off-by: Simon Glass 
Tested-by: Philipp Tomsich

patman: Make print statements python 3.x safe

2016-10-09T15:30:32+00:00

In python 3.x, print must be used as a function call. Convert all print
statements to the function call style, importing from __future__ where
we print with no trailing newline or print to a file object.

Signed-off-by: Paul Burton 
Acked-by: Simon Glass