From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Tony Lindgren <tony@atomide.com>, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [kbuild-all] Re: drivers/net/wireless/ti/wlcore/main.c:700:9: sparse: sparse: context imbalance in 'wlcore_irq' - different lock contexts for basic block
Date: Thu, 20 Aug 2020 08:34:37 +0800 [thread overview]
Message-ID: <a817204f-8b4d-339f-6e22-701ed189795b@intel.com> (raw)
In-Reply-To: <20200817102821.GE2994@atomide.com>
On 8/17/2020 6:28 PM, Tony Lindgren wrote:
> Hi,
>
> * kernel test robot <lkp@intel.com> [200811 11:55]:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 00e4db51259a5f936fec1424b884f029479d3981
>> commit: 35fba0f0fd762a8b87d403ae3c723e0061c4aa25 wlcore: Use spin_trylock in wlcore_irq() to see if we need to queue tx
>> date: 4 weeks ago
>> config: mips-randconfig-s032-20200811 (attached as .config)
>> compiler: mips64-linux-gcc (GCC) 9.3.0
>> reproduce:
>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> # apt-get install sparse
>> # sparse version: v0.6.2-168-g9554805c-dirty
>> git checkout 35fba0f0fd762a8b87d403ae3c723e0061c4aa25
>> # save the attached .config to linux build tree
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=mips
>>
>> 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/ti/wlcore/main.c:643:34: sparse: sparse: context imbalance in 'wlcore_irq_locked' - different lock contexts for basic block
>>>> drivers/net/wireless/ti/wlcore/main.c:700:9: sparse: sparse: context imbalance in 'wlcore_irq' - different lock contexts for basic block
> I tried to reproduce this with cross compiling for ARM using sparse-0.6.2,
> but don't see any similar warnings.
>
> Is this only happening on mips for some reason?
>
> Regards,
>
> Tony
>
Hi Tony,
Sorry for the inconvenience, please ignore this report,
there is something wrong in the bot.
Best Regards,
Rong Chen
prev parent reply other threads:[~2020-08-20 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 11:54 kernel test robot
2020-08-17 10:28 ` Tony Lindgren
2020-08-20 0:34 ` Chen, Rong A [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=a817204f-8b4d-339f-6e22-701ed189795b@intel.com \
--to=rong.a.chen@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®