From: David Miller <davem@davemloft.net>
To: jarkao2@o2.pl
Cc: jura@netams.com, akpm@linux-foundation.org,
netdev@vger.kernel.org, paulus@samba.org,
greearb@candelatech.com, mostrows@speakeasy.net
Subject: Re: [PATCH] vlan: lockdep subclass for ppp _xmit_lock Re: ppp_generic: fix lockdep warning
Date: Wed, 09 May 2007 02:32:24 -0700 (PDT) [thread overview]
Message-ID: <20070509.023224.31601789.davem@davemloft.net> (raw)
In-Reply-To: <20070509093536.GA2436@ff.dom.local>
From: Jarek Poplawski <jarkao2@o2.pl>
Date: Wed, 9 May 2007 11:35:37 +0200
> After rethinking there is the 3-rd way (as usual):
>
> c) vlan should use different lockdep lock subclasses or
> classes for different types of devices, used at the same
> time.
Perhaps we should just bite the bullet and use a seperate
unique lock class for ->_xmit_lock of each device type.
We are going to find more cases like this one, for sure.
next prev parent reply other threads:[~2007-05-09 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 7:27 [patch 10/15] ppp_generic: fix lockdep warning akpm
2007-04-26 8:39 ` David Miller
2007-04-26 10:49 ` Jarek Poplawski
2007-05-09 9:35 ` [PATCH] vlan: lockdep subclass for ppp _xmit_lock " Jarek Poplawski
2007-05-09 9:32 ` David Miller [this message]
2007-05-09 13:13 ` [PATCH (take 2)] vlan: lockdep class " Jarek Poplawski
2007-05-09 20:06 ` [PATCH] vlan: lockdep subclass " Yuriy N. Shkandybin
2007-05-10 5:30 ` Jarek Poplawski
2007-05-10 6:03 ` Yuriy N. Shkandybin
2007-05-10 6:39 ` Jarek Poplawski
2007-05-11 7:00 ` [PATCH] ppp_generic: lockdep class " Jarek Poplawski
2007-04-26 10:04 ` [patch 10/15] " Paul Mackerras
2007-04-26 11:28 ` Jarek Poplawski
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=20070509.023224.31601789.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=greearb@candelatech.com \
--cc=jarkao2@o2.pl \
--cc=jura@netams.com \
--cc=mostrows@speakeasy.net \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).