From: Jens Axboe <axboe@suse.de>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre5 not easy to boot with devfs
Date: Mon, 3 Dec 2001 21:52:02 +0100 [thread overview]
Message-ID: <20011203215202.G5176@suse.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0112021150310.12801-100000@binet.math.psu.edu> <E16AaCR-0003wy-00@the-village.bc.nu> <200112021802.fB2I2iE10476@vindaloo.ras.ucalgary.ca> <20011203135842.A5176@suse.de> <200112031906.fB3J6X323874@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200112031906.fB3J6X323874@vindaloo.ras.ucalgary.ca>
On Mon, Dec 03 2001, Richard Gooch wrote:
> Jens Axboe writes:
> > On Sun, Dec 02 2001, Richard Gooch wrote:
> > > And 2.5 isn't going to get a lot of testing until the breakage caused
> > > by the bio changes is fixed. At the moment, I can't even test it
> > > myself.
> >
> > I'll just go read your bug rapport and fix it right up.
>
> It wasn't meant as a criticism of the changes. I'm glad to see someone
> working on fixing the bio layer. It's just not ready for widespread
> testing yet (crude measurement: if it breaks for me, it's not ready
> for the masses ;-). Once I surface from this round of devfs cleanups,
> I'll pause for breath and try again with 2.5. If I still have
> problems, I'll let you know.
No seriously, I want to know if something is broken so it can get fixed.
bio core is indeed stable, if something breaks it's drivers. And they
need fixing right away.
At least until I break every single block driver out there again in a
few days. And no, I'm not kidding.
--
Jens Axboe
next prev parent reply other threads:[~2001-12-04 1:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 4:43 2.5.1-pre5 not easy to boot with devfs Pierre Rousselet
2001-12-01 5:01 ` Alexander Viro
2001-12-01 5:37 ` Linus Torvalds
2001-12-01 7:01 ` Richard Gooch
2001-12-01 8:45 ` Pierre Rousselet
2001-12-01 18:36 ` Richard Gooch
2001-12-01 20:37 ` Pierre Rousselet
2001-12-01 23:20 ` Richard Gooch
2001-12-02 1:11 ` Pierre Rousselet
2001-12-02 10:28 ` Pierre Rousselet
2001-12-02 16:59 ` Alexander Viro
2001-12-02 17:14 ` Alan Cox
2001-12-02 18:02 ` Richard Gooch
2001-12-03 12:58 ` Jens Axboe
2001-12-03 19:06 ` Richard Gooch
2001-12-03 20:52 ` Jens Axboe [this message]
2001-12-02 17:55 ` Richard Gooch
2001-12-03 19:54 ` Alexander Viro
2001-12-02 22:57 ` Keith Owens
2001-12-03 4:50 ` Pierre Rousselet
2001-12-02 8:05 ` Pierre Rousselet
2001-12-01 23:47 ` Richard Gooch
2001-12-02 7:11 ` Pierre Rousselet
2001-12-02 21:22 ` Richard Gooch
2001-12-02 9:27 ` Pierre Rousselet
2001-12-02 19:40 ` Bongani Hlope
2001-12-01 9:59 ` Pierre Rousselet
2001-12-03 6:33 ` Richard Gooch
2001-12-03 5:57 ` Pierre ROUSSELET
2001-12-03 12:16 ` Pierre Rousselet
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=20011203215202.G5176@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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