From: Matthew Wilcox <willy@debian.org>
To: Dag Nygren <dag@newtech.fi>
Cc: Matthew Wilcox <willy@debian.org>,
"Randy.Dunlap" <rddunlap@osdl.org>,
linux-scsi@vger.kernel.org
Subject: Re: Bug in the sg driver
Date: Tue, 7 Oct 2003 13:26:23 +0100 [thread overview]
Message-ID: <20031007122623.GJ24824@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20031007120355.19343.qmail@dag.newtech.fi>
On Tue, Oct 07, 2003 at 03:03:55PM +0300, Dag Nygren wrote:
> > On Tue, Oct 07, 2003 at 08:47:00AM +0300, Dag Nygren wrote:
>
> > Then you really should be taking these problems up with Red Hat,
> > not with us.
>
> So you mean that this bug is squished in 2.4.22 then?
Not necessarily. Red Hat's kernels contain a lot of customisations and
changes versus the stock Linux tree. It's almost impossible for us to
debug problems in Red Hat's kernel. It's possible (though unlikely)
the bug was even introduced by Red Hat.
In any case, if you need a Red Hat supplied kernel, you need to work
with Red Hat. There's really no way around that.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-10-07 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031006180636.16530.qmail@dag.newtech.fi>
2003-10-06 18:20 ` Bug in the sg driver Randy.Dunlap
2003-10-06 18:47 ` Dag Nygren
2003-10-06 18:52 ` Randy.Dunlap
2003-10-06 19:11 ` Dag Nygren
2003-10-06 22:18 ` Randy.Dunlap
2003-10-07 5:47 ` Dag Nygren
2003-10-07 11:56 ` Matthew Wilcox
2003-10-07 12:03 ` Dag Nygren
2003-10-07 12:26 ` Matthew Wilcox [this message]
2003-10-07 12:37 ` Douglas Gilbert
2003-10-07 12:50 ` Dag Nygren
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=20031007122623.GJ24824@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=dag@newtech.fi \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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