From: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: dag@newtech.fi, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Bug in the sg driver
Date: Mon, 6 Oct 2003 11:52:45 -0700 [thread overview]
Message-ID: <20031006115245.17d73f0c.rddunlap@osdl.org> (raw)
In-Reply-To: <20031006184742.18117.qmail@dag.newtech.fi>
On Mon, 06 Oct 2003 21:47:42 +0300 Dag Nygren <dag@newtech.fi> wrote:
| >
| > from MAINTAINERS file:
| > SCSI SG DRIVER
| > P: Doug Gilbert
| > M: dgilbert@interlog.com
| > L: linux-scsi@vger.kernel.org
| > W: http://www.torque.net/sg
| > S: Maintained
|
| Should I send a bug report to him or is he online here?
Um, if he's around, he'll see it, although ISTR that he's away
for awhile (like 6 weeks ?).
| > Any details, like kernel version, oops or panic logs, etc.?
|
| Kernel version is 2.4.20 (Redhat 9.0 + newest upgrade)
|
| The oops and the panic logs were not written down as the major focus
| was getting this (production) system up and running, sorry for that
Well, unless someone happens to know something about your exact
reported problem....
in general, you will get better help/responses the better your
problem reports are (IMHO).
--
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Dag Nygren <dag@newtech.fi>
Cc: dag@newtech.fi, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Bug in the sg driver
Date: Mon, 6 Oct 2003 11:52:45 -0700 [thread overview]
Message-ID: <20031006115245.17d73f0c.rddunlap@osdl.org> (raw)
In-Reply-To: <20031006184742.18117.qmail@dag.newtech.fi>
On Mon, 06 Oct 2003 21:47:42 +0300 Dag Nygren <dag@newtech.fi> wrote:
| >
| > from MAINTAINERS file:
| > SCSI SG DRIVER
| > P: Doug Gilbert
| > M: dgilbert@interlog.com
| > L: linux-scsi@vger.kernel.org
| > W: http://www.torque.net/sg
| > S: Maintained
|
| Should I send a bug report to him or is he online here?
Um, if he's around, he'll see it, although ISTR that he's away
for awhile (like 6 weeks ?).
| > Any details, like kernel version, oops or panic logs, etc.?
|
| Kernel version is 2.4.20 (Redhat 9.0 + newest upgrade)
|
| The oops and the panic logs were not written down as the major focus
| was getting this (production) system up and running, sorry for that
Well, unless someone happens to know something about your exact
reported problem....
in general, you will get better help/responses the better your
problem reports are (IMHO).
--
~Randy
next prev parent reply other threads:[~2003-10-06 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 18:06 Bug in the sg driver Dag Nygren
2003-10-06 18:20 ` Randy.Dunlap
2003-10-06 18:47 ` Dag Nygren
2003-10-06 18:47 ` Dag Nygren
2003-10-06 18:52 ` Randy.Dunlap [this message]
2003-10-06 18:52 ` Randy.Dunlap
2003-10-06 19:11 ` Dag Nygren
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
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=20031006115245.17d73f0c.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=dag@newtech.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.