ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tamizh Chelvam <tamizhr@codeaurora.org>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, kbuild-all@lists.01.org
Subject: Re: [PATCH 3/4] ath10k: Add new api to support TID specific configuration
Date: Mon, 29 Jun 2020 18:02:52 +0800	[thread overview]
Message-ID: <202006291741.qvgw0oBs%lkp@intel.com> (raw)
In-Reply-To: <1593363718-5148-4-git-send-email-tamizhr@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

Hi Tamizh,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on ath6kl/ath-next]
[also build test WARNING on wireless-drivers-next/master v5.8-rc3 next-20200629]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use  as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Tamizh-Chelvam/ath10k-Add-support-for-TID-specific-configuration/20200629-010528
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath-next
config: x86_64-randconfig-s021-20200629 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.2-3-gfa153962-dirty
        # save the attached .config to linux build tree
        make W=1 C= CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> drivers/net/wireless/ath/ath10k/mac.c:6864:5: sparse: sparse: symbol 'ath10k_mac_set_tid_config' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35866 bytes --]

[-- Attachment #3: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2020-06-29 10:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 17:01 [PATCH 0/4] ath10k: Add support for TID specific configuration Tamizh Chelvam
2020-06-28 17:01 ` [PATCH 1/4] ath10k: Add wmi command support for station specific TID config Tamizh Chelvam
2020-06-28 17:01 ` [PATCH 2/4] ath10k: Move rate mask validation function up in the file Tamizh Chelvam
2020-06-28 17:01 ` [PATCH 3/4] ath10k: Add new api to support TID specific configuration Tamizh Chelvam
2020-06-29  8:39   ` kernel test robot
2020-06-29 10:02   ` kernel test robot [this message]
2020-06-29 10:02   ` [RFC PATCH] ath10k: ath10k_mac_set_tid_config() can be static kernel test robot
2020-06-28 17:01 ` [PATCH 4/4] ath10k: Add new api to support reset TID config Tamizh Chelvam
2020-06-29  9:11   ` kernel test robot

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=202006291741.qvgw0oBs%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tamizhr@codeaurora.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).