Linux wireless drivers development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alex Briskin <br.shurik@gmail.com>
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org,
	johannes@sipsolutions.net, Alex Briskin <br.shurik@gmail.com>
Subject: Re: [PATCH 3/4 v1] Continue breaking down to smaller functions
Date: Thu, 14 Jul 2016 04:41:20 +0800	[thread overview]
Message-ID: <201607140412.rPdRBs25%fengguang.wu@intel.com> (raw)
In-Reply-To: <1468441196-23503-4-git-send-email-br.shurik@gmail.com>

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

Hi,

[auto build test WARNING on mac80211/master]
[also build test WARNING on v4.7-rc7]
[cannot apply to mac80211-next/master next-20160712]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Alex-Briskin/Refactoring-ieee80211_iface_work/20160714-042301
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git master
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=sparc64 

All warnings (new ones prefixed by >>):

   net/mac80211/iface.c: In function 'ieee80211_iface_work':
>> net/mac80211/iface.c:1333:19: warning: unused variable 'sta' [-Wunused-variable]
     struct sta_info *sta;
                      ^

vim +/sta +1333 net/mac80211/iface.c

  1317							       WLAN_REASON_QSTA_REQUIRE_SETUP,
  1318							       true);
  1319			}
  1320			mutex_unlock(&local->sta_mtx);
  1321		} else {
  1322			return false;
  1323		}
  1324		return true;
  1325	}
  1326	
  1327	static void ieee80211_iface_work(struct work_struct *work)
  1328	{
  1329		struct ieee80211_sub_if_data *sdata =
  1330			container_of(work, struct ieee80211_sub_if_data, work);
  1331		struct ieee80211_local *local = sdata->local;
  1332		struct sk_buff *skb;
> 1333		struct sta_info *sta;
  1334	
  1335		if (!ieee80211_sdata_running(sdata))
  1336			return;
  1337	
  1338		if (test_bit(SCAN_SW_SCANNING, &local->scanning))
  1339			return;
  1340	
  1341		if (!ieee80211_can_run_worker(local))

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

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 46212 bytes --]

  reply	other threads:[~2016-07-13 20:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 20:19 [PATCH 0/4 v1] Refactoring ieee80211_iface_work Alex Briskin
2016-07-13 20:19 ` [PATCH 1/4 v1] Refactoring ieee80211_iface_work to reduce complexity and improve readability Alex Briskin
2016-07-13 20:19 ` [PATCH 2/4 v1] even better readability Alex Briskin
2016-07-13 20:19 ` [PATCH 3/4 v1] Continue breaking down to smaller functions Alex Briskin
2016-07-13 20:41   ` kbuild test robot [this message]
2016-07-13 20:19 ` [PATCH 4/4 v1] Simple and well understood logic Alex Briskin
2016-07-14  7:56 ` [PATCH 0/4 v1] Refactoring ieee80211_iface_work Arend Van Spriel
2016-07-14 13:04   ` Alex Briskin

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=201607140412.rPdRBs25%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=br.shurik@gmail.com \
    --cc=johannes@sipsolutions.net \
    --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