public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2•pl>
To: "Yuriy N\. Shkandybin" <jura@netams•com>
Cc: akpm@linux-foundation•org, netdev@vger•kernel.org,
	paulus@samba•org, greearb@candelatech•com,
	mostrows@speakeasy•net, davem@davemloft•net
Subject: Re: [PATCH] vlan: lockdep subclass for ppp _xmit_lock Re: ppp_generic: fix lockdep warning
Date: Thu, 10 May 2007 08:39:08 +0200	[thread overview]
Message-ID: <20070510063908.GA2021@ff.dom.local> (raw)
In-Reply-To: <049301c792c8$ecdf4c40$0202fea9@Jura>

On Thu, May 10, 2007 at 10:03:23AM +0400, Yuriy N. Shkandybin wrote:
> Yes, there is no real lockup with pppoe
> ll repeat my configuration:
> vpn (pptp(mostly)+pppoe) concentrator
> PPPoE provided through 802.1q
> +OSPF (quagga)

I think, it's a little too general... Probably at least
ifconfig and ip rule, route etc. could tell something.
But let's wait a little.

Jarek P.

  reply	other threads:[~2007-05-10  6:32 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
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 [this message]
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=20070510063908.GA2021@ff.dom.local \
    --to=jarkao2@o2$(echo .)pl \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=greearb@candelatech$(echo .)com \
    --cc=jura@netams$(echo .)com \
    --cc=mostrows@speakeasy$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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