public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, jgarzik@mandrakesoft.com,
	akpm@zip.com.au, buytenh@gnu.org
Subject: Re: [BUG] DEADLOCK when removing a bridge on 2.4.19-pre6
Date: Thu, 11 Apr 2002 13:24:16 -0700	[thread overview]
Message-ID: <20020411202416.GN23513@matchmail.com> (raw)
In-Reply-To: <20020411004911.GH23513@matchmail.com> <20020411010515.GI23513@matchmail.com> <20020411014035.GJ23513@matchmail.com> <20020410.194411.48882878.davem@redhat.com>

On Wed, Apr 10, 2002 at 07:44:11PM -0700, David S. Miller wrote:
>    From: Mike Fedyk <mfedyk@matchmail.com>
>    Date: Wed, 10 Apr 2002 18:40:35 -0700
> 
>    On Wed, Apr 10, 2002 at 06:05:15PM -0700, Mike Fedyk wrote:
>    > 2.4.19-pre6-nobr0fpsh building now...
>    
>    Yep, reversing 2.4.18_fix_port_state_handling.diff fixed it.
> 
> Thanks for tracking this down so precisely.  If every bug reporter
> actually bothered to do this work, it'd take a lot less work to
> fix most bugs :-)
>

Thanks. :)

> Lennert, just let me know when you have a fix :-)
> 

Couldn't have done it if Lennert didn't keep those applied patches
available, and separated. :)

Mike

  reply	other threads:[~2002-04-11 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10  1:53 [BUG] DEADLOCK when removing a bridge on 2.4.19-pre6 Mike Fedyk
2002-04-10  3:57 ` Andreas Dilger
2002-04-10 15:00 ` Lennert Buytenhek
2002-04-10 18:16 ` Mike Fedyk
2002-04-11  0:49   ` Mike Fedyk
2002-04-11  1:05     ` Mike Fedyk
2002-04-11  1:40       ` Mike Fedyk
2002-04-11  2:44         ` David S. Miller
2002-04-11 20:24           ` Mike Fedyk [this message]
2002-04-23 23:00         ` [PATCH] " Mike Fedyk

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=20020411202416.GN23513@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=akpm@zip.com.au \
    --cc=buytenh@gnu.org \
    --cc=davem@redhat.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.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