From: Deepak Mishra <linux.dkm@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Checkpatch.pl FAIL: "Blob or Tree named 'other' not found"
Date: Sun, 12 May 2019 11:45:24 +0530 [thread overview]
Message-ID: <CAHkoDDYdcKpyF57a3Wcw1aULbGHnNqQ5-7BpC2AfeBtoHXKrSQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1157 bytes --]
Hi all,
I am trying to run checkpatch.pl on latest kernel version 5.1.0 source tree
from orig head 80f232121b69cc69a31ccb2b38c1665d770b0710
When I run checkpatch.pl, for every file I get the follwong or similar
error. Could you please help if this is my environment issue or actually
error in code which I need to fix ?
I executed the following in command prompt.
perl scripts/checkpatch.pl -f drivers/staging/rtl8712/* |less
The error I observe
drivers/staging/rtl8712/rtl871x_rf.h
------------------------------------
FAIL: "Blob or Tree named 'other' not found"
Traceback (most recent call last):
File "scripts/spdxcheck.py", line 240, in <module>
spdx = read_spdxdata(repo)
File "scripts/spdxcheck.py", line 41, in read_spdxdata
for el in lictree[d].traverse():
File "/usr/lib/python2.7/dist-packages/git/objects/tree.py", line 298, in
__getitem__
return self.join(item)
File "/usr/lib/python2.7/dist-packages/git/objects/tree.py", line 244, in
join
raise KeyError(msg % file)
KeyError: "Blob or Tree named 'other' not found"
total: 0 errors, 0 warnings, 0 checks, 56 lines checked
Please suggest me.
Best Regards
Mishradk
[-- Attachment #1.2: Type: text/html, Size: 1851 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2019-05-12 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 6:15 Deepak Mishra [this message]
2019-05-12 7:41 ` Checkpatch.pl FAIL: "Blob or Tree named 'other' not found" Valdis Klētnieks
2019-05-12 8:15 ` Deepak Mishra
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=CAHkoDDYdcKpyF57a3Wcw1aULbGHnNqQ5-7BpC2AfeBtoHXKrSQ@mail.gmail.com \
--to=linux.dkm@gmail.com \
--cc=kernelnewbies@kernelnewbies.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).