linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets
Date: Fri, 06 Apr 2018 11:09:12 +0300	[thread overview]
Message-ID: <87d0zcsqmv.fsf@codeaurora.org> (raw)
In-Reply-To: <1d917688-9f59-39ad-46a6-527d9e3dec03@dd-wrt.com> (Sebastian Gottschall's message of "Thu, 5 Apr 2018 22:27:18 +0200")

(adding back the lists, please don't top post and trim your quotes)

Sebastian Gottschall <s.gottschall@dd-wrt.com> writes:

> okay. ath10k-check is buggy and doesnt work. so it doesnt help much
> with code styles
>
> root@seg-desktop:/xfs/ath10k/ath.gpio# ./ath10k-check
> global: 'drivers/net/wireless/ath/ath10k/Kconfig' is not a source file.
> Traceback (most recent call last):
> =C2=A0 File "./ath10k-check", line 461, in <module>
> =C2=A0=C2=A0=C2=A0 main()
> =C2=A0 File "./ath10k-check", line 455, in main
> =C2=A0=C2=A0=C2=A0 ret =3D run_checkpatch(args)
> =C2=A0 File "./ath10k-check", line 275, in run_checkpatch
> =C2=A0=C2=A0=C2=A0 output =3D subprocess.check_output(cmd, shell=3DTrue)
> =C2=A0 File "/usr/lib/python2.7/subprocess.py", line 219, in check_output
> =C2=A0=C2=A0=C2=A0 raise CalledProcessError(retcode, cmd, output=3Doutput)
> subprocess.CalledProcessError: Command 'global -f=20
> drivers/net/wireless/ath/ath10k/Kconfig' returned non-zero exit status 1

You are missing gtags, see 'ath10k-check --help' for how to install:

Requirements (all available in $PATH):

* gcc
* sparse
* checkpatch.pl
* gtags (from package global)

--=20
Kalle Valo

  parent reply	other threads:[~2018-04-06  8:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  8:44 [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets s.gottschall
2018-02-27 17:03 ` Steve deRosier
2018-02-27 17:43   ` Sebastian Gottschall
2018-02-27 22:08 ` Rafał Miłecki
2018-02-28  1:49   ` Sebastian Gottschall
2018-03-02  9:03     ` Pavel Machek
2018-03-02  9:22       ` Sebastian Gottschall
2018-03-07 16:22         ` Rafał Miłecki
2018-03-07 17:54           ` Sebastian Gottschall
2018-03-08  9:02             ` Pavel Machek
2018-03-08 12:33               ` Sebastian Gottschall
2018-03-08 14:05                 ` Pavel Machek
2018-03-08 14:29                   ` Kalle Valo
2018-03-08 14:43                     ` Sebastian Gottschall
2018-03-08 14:34                   ` Sebastian Gottschall
2018-03-08 15:04                     ` Pavel Machek
2018-03-08 15:31                       ` Sebastian Gottschall
2018-03-08 15:46                   ` Felix Fietkau
2018-03-10  7:44                     ` Julian Calaby
2018-03-10  7:56                       ` Sebastian Gottschall
2018-03-12  7:53                         ` Mathias Kresin
2018-03-12  9:09                           ` Sebastian Gottschall
2018-04-05 14:44 ` Kalle Valo
2018-04-05 18:01   ` Sebastian Gottschall
2018-04-05 20:00     ` Sebastian Gottschall
2018-04-06  8:07       ` Kalle Valo
2018-04-06  8:10         ` Sebastian Gottschall
     [not found]       ` <1d917688-9f59-39ad-46a6-527d9e3dec03@dd-wrt.com>
2018-04-06  8:09         ` Kalle Valo [this message]
2018-04-06  8:11           ` Sebastian Gottschall
2018-04-06  8:25             ` Kalle Valo
     [not found]               ` <f3617290-34d5-0cca-6442-4a37c06701b1@dd-wrt.com>
2018-04-06  9:17                 ` Kalle Valo
2018-04-06  8:05     ` Kalle Valo

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=87d0zcsqmv.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.gottschall@dd-wrt.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).