public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Josh McKinney <forming@home.com>,
	linux-kernel@vger.kernel.org,
	Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: Fwd: binutils in debian unstable is broken.
Date: Wed, 5 Dec 2001 02:58:40 -0800	[thread overview]
Message-ID: <20011205105840.GA439@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011205050513.GD1442@cy599856-a.home.com> <3C0DB3D6.9C86B865@zip.com.au> <3C0DC1AA.E653D425@zip.com.au>
In-Reply-To: <3C0DC1AA.E653D425@zip.com.au>

On Tue, Dec 04, 2001 at 10:41:46PM -0800, Andrew Morton wrote:
> Andrew Morton wrote:
> > 
> > 3) Something else.  HJ's #ifdef MODULE works OK.  It has a rather
> >    internecine relationship with the workings of __devexit though.
> 
> OK, here's a piece of speed-editing.  Fixed a few other __devexit
> bugs on the way as well.
> 

Thanks Andrew, you fixed it before I had the compulsion to compile a new
kernel.

I'm running 2.4.17-pre2+ext3-0.9.16+binutils now, and all is well so far.

Mike

  parent reply	other threads:[~2001-12-05 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05  5:05 Fwd: binutils in debian unstable is broken Josh McKinney
2001-12-05  5:20 ` Daniel T. Chen
2001-12-05  5:42 ` Andrew Morton
2001-12-05  6:41   ` Andrew Morton
2001-12-05  9:37     ` eddantes
2001-12-05 10:58     ` Mike Fedyk [this message]
2001-12-05  8:43   ` Alan Cox
2001-12-05  9:49     ` Jakub Jelinek
2001-12-05 13:34     ` Eric Lammerts
2001-12-05 14:18       ` Jeff Garzik
2001-12-06 15:09       ` Kai Germaschewski
2001-12-05 14:38 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2001-12-05  5:19 Frédéric L. W. Meunier
2001-12-05  5:25 ` Daniel T. Chen

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=20011205105840.GA439@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=akpm@zip.com.au \
    --cc=forming@home.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