From: Diederik de Haas <didi.debian@cknow.org>
To: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-kernel@vger.kernel.org,
Diederik de Haas <didi.debian@cknow.org>
Subject: checkpatch: diff: LICENSES/null: No such file or directory
Date: Thu, 29 Jun 2023 11:57:49 +0200 [thread overview]
Message-ID: <8238840.T7Z3S40VBb@bagend> (raw)
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Hi,
The checkpatch.pl scripts has been a great help in improving the (very bad)
quality of some code I'm helping with, so thanks for that :-)
But it looks like I found a bug after I added a LICENSES dir and a
GPL-2.0-only license using the `reuse` tool. When I run this command:
~/dev/kernel.org/linux/scripts/checkpatch.pl --no-tree --file --terse *
in my working tree, I get "diff: LICENSES/null: No such file or directory"
after which it stops processing the rest of the files.
To reproduce:
1) git clone https://git.sr.ht/~diederik/bes2600 -b improve-code-formatting
2) cd bes2600
3) ~/dev/kernel.org/linux/scripts/checkpatch.pl --no-tree --file --terse *
If you then do `git reset HEAD~2 --hard` and run `checkpatch.pl` again, it'll
finish to completion.
I just did a similar test inside the kernel tree, and got a similar error:
- `scripts/checkpatch.pl --file --terse *`
- result: `diff: arch/null: No such file or directory`
As my LICENSES dir was my first subdirectory, it appears the issue is with
subdirectories in general?
Cheers,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2023-06-29 10:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8238840.T7Z3S40VBb@bagend \
--to=didi.debian@cknow.org \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.