From: David Miller <davem@davemloft.net>
To: jacob.e.keller@intel.com
Cc: vyasevic@redhat.com, netdev@vger.kernel.org,
dingtianhong@huawei.com, vfalico@gmail.com, kaber@trash.net,
jiri@resnulli.us
Subject: Re: [PATCH v3 2/4] net: Allow for more then a single subclass for netif_addr_lock
Date: Wed, 04 Jun 2014 14:53:44 -0700 (PDT) [thread overview]
Message-ID: <20140604.145344.1776321352568977848.davem@davemloft.net> (raw)
In-Reply-To: <1401918131.24086.9.camel@jekeller-desk1.amr.corp.intel.com>
From: "Keller, Jacob E" <jacob.e.keller@intel.com>
Date: Wed, 4 Jun 2014 21:42:12 +0000
> This only occurs if CONFIG_DEBUG_LOCK_ALLOC=Y, and there seems to be no
> easy fix for the warning, due to how spin_lock_nested is a macro that
> discards the second parameter when DEBUG_LOCK_ALLOC is disabled.
spin_lock_nested(), in that case, should mark the argument as unused.
next prev parent reply other threads:[~2014-06-04 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 21:04 [PATCH v3 0/4] Fix lockdep issues with stacked devices Vlad Yasevich
2014-05-16 21:04 ` [PATCH v3 1/4] net: Find the nesting level of a given device by type Vlad Yasevich
2014-05-17 2:16 ` David Miller
2014-05-16 21:04 ` [PATCH v3 2/4] net: Allow for more then a single subclass for netif_addr_lock Vlad Yasevich
2014-06-04 21:42 ` Keller, Jacob E
2014-06-04 21:53 ` David Miller [this message]
2014-06-04 22:50 ` Keller, Jacob E
2014-06-04 23:17 ` Vlad Yasevich
2014-05-16 21:04 ` [PATCH v3 3/4] vlan: Fix lockdep warning with stacked vlan devices Vlad Yasevich
2014-05-16 21:04 ` [PATCH v3 4/4] macvlan: Fix lockdep warnings with stacked macvlan devices Vlad Yasevich
2014-05-18 16:36 ` Patrick McHardy
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=20140604.145344.1776321352568977848.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.com \
--cc=vyasevic@redhat.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;
as well as URLs for NNTP newsgroup(s).