Linux wireless drivers development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: greearb@candelatech.com
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org,
	ath6kl@lists.infradead.org, Ben Greear <greearb@candelatech.com>
Subject: Re: [PATCH 2/2] ath6k: implement ethtool stats.
Date: Thu, 22 Oct 2015 08:58:58 +0800	[thread overview]
Message-ID: <201510220815.XZd9VwIK%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445471597-26091-2-git-send-email-greearb@candelatech.com>

Hi Ben,

[auto build test WARNING on net/master -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/greearb-candelatech-com/ath6k-break-stats-gathering-code-into-separate-method/20151022-075558
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/net/wireless/ath/ath6kl/cfg80211.c:3750:26: sparse: symbol 'ath6k_ethtool_ops' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  reply	other threads:[~2015-10-22  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 23:53 [PATCH 1/2] ath6k: break stats gathering code into separate method greearb
2015-10-21 23:53 ` [PATCH 2/2] ath6k: implement ethtool stats greearb
2015-10-22  0:58   ` kbuild test robot [this message]
2015-10-22  0:58   ` [RFC PATCH] ath6k: ath6k_ethtool_ops can be static kbuild 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=201510220815.XZd9VwIK%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ath6kl@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --cc=kbuild-all@01.org \
    --cc=linux-wireless@vger.kernel.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