Linux wireless drivers development
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [wireless-next:master 196/214] drivers/net/wireless/brcm80211/brcmsmac/main.c:308:10: sparse: symbol 'wlc_prio2prec_map' was not declared. Should it be static?
Date: Wed, 21 Nov 2012 08:12:49 -0600	[thread overview]
Message-ID: <20121121141249.GA23606@thinkpad-t410> (raw)
In-Reply-To: <50ac7bc7.tSErItiXQxTyHiGi%fengguang.wu@intel.com>

On Wed, Nov 21, 2012 at 02:59:19PM +0800, kbuild test robot wrote:
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git master
> head:   e2ff0498409af6f2023f91aba07b281e5e87ee15
> commit: e041f65d5f00011049c7d6af0e31ce69ce9e2655 [196/214] brcmsmac: Remove internal tx queue
> 
> 
> sparse warnings:
> 
> + drivers/net/wireless/brcm80211/brcmsmac/main.c:308:10: sparse: symbol 'wlc_prio2prec_map' was not declared. Should it be static?
> drivers/net/wireless/brcm80211/brcmsmac/main.c:6500:43:   also defined here
> 
> Please consider folding the attached diff :-)

Actually this just isn't used anymore. I'll send a patch to remove it
next week when I'm back from holiday.

Seth


      reply	other threads:[~2012-11-21 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21  6:59 [wireless-next:master 196/214] drivers/net/wireless/brcm80211/brcmsmac/main.c:308:10: sparse: symbol 'wlc_prio2prec_map' was not declared. Should it be static? kbuild test robot
2012-11-21 14:12 ` Seth Forshee [this message]

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=20121121141249.GA23606@thinkpad-t410 \
    --to=seth.forshee@canonical.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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