kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Deepak Mishra <linux.dkm@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Checkpatch.pl FAIL: "Blob or Tree named 'other' not found"
Date: Sun, 12 May 2019 03:41:55 -0400	[thread overview]
Message-ID: <2090.1557646915@turing-police> (raw)
In-Reply-To: <CAHkoDDYdcKpyF57a3Wcw1aULbGHnNqQ5-7BpC2AfeBtoHXKrSQ@mail.gmail.com>

On Sun, 12 May 2019 11:45:24 +0530, Deepak Mishra said:

> 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

Found the problem, patch submitted.  It's a one-line fix:

diff --git a/scripts/spdxcheck.py b/scripts/spdxcheck.py
index 4fe392e507fb..7abd5f5cb14d 100755
--- a/scripts/spdxcheck.py
+++ b/scripts/spdxcheck.py
@@ -32,7 +32,7 @@ import os
 def read_spdxdata(repo):
 
     # The subdirectories of LICENSES in the kernel source
-    license_dirs = [ "preferred", "other", "exceptions" ]
+    license_dirs = [ "preferred", "dual", "deprecated", "exceptions" ]
     lictree = repo.head.commit.tree['LICENSES']





_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2019-05-12  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-12  6:15 Checkpatch.pl FAIL: "Blob or Tree named 'other' not found" Deepak Mishra
2019-05-12  7:41 ` Valdis Klētnieks [this message]
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=2090.1557646915@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux.dkm@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 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).