public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	linux-kernel@vger.kernel.org
Subject: Re: [-ENOCOMPILE] ataraid as module in linux-2.5.7-pre2
Date: Mon, 18 Mar 2002 18:37:59 +0100	[thread overview]
Message-ID: <20020318183759.E17410@suse.de> (raw)
In-Reply-To: <200203180938.g2I9c1q27846@Port.imtp.ilyichevsk.odessa.ua> <20020318142240.D3025@suse.de> <200203181341.g2IDfbq28679@Port.imtp.ilyichevsk.odessa.ua> <20020318145313.E3025@suse.de> <20020318164215.GI2254@matchmail.com> <20020318174527.C17410@suse.de> <20020318172304.GJ2254@matchmail.com>

 >     * Some reports of unknown cause of ext2 corruption since 2.5.3 (not
 > related to the missing i_fsize clearing from .3pre3-5)
 > 
 > It would be good to report the last version that this problem was reported
 > against, and this type of problem can't really be tested on each pre patch.
 > That's basically what I was asking for before...

Gotcha. Point taken.

 > # IDE floppy oops on some (zip100) setups. (Triggers BUG_ON() in
 > elevator.c:237)
 > 
 > If the version is reported for this then you can see what function was being
 > reported at the time.  Otherwise some other patch could shift the contents
 > to make line 237 point to another function (rewrites and such...)

 I'll make those BUG() descriptions include the function name & BUG condition
 in future descriptions.

 Thanks for the feedback
-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

      reply	other threads:[~2002-03-18 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 13:37 [-ENOCOMPILE] ataraid as module in linux-2.5.7-pre2 Denis Vlasenko
2002-03-18 13:22 ` Dave Jones
2002-03-18 17:41   ` Denis Vlasenko
2002-03-18 13:53     ` Dave Jones
2002-03-18 16:42       ` Mike Fedyk
2002-03-18 16:45         ` Dave Jones
2002-03-18 17:23           ` Mike Fedyk
2002-03-18 17:37             ` Dave Jones [this message]

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=20020318183759.E17410@suse.de \
    --to=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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