From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Duncan Laurie <duncan@sun.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: problem with Serverworks CSB5 IDE
Date: 28 Apr 2003 14:03:53 +0100 [thread overview]
Message-ID: <1051535033.16809.15.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3EA983F3.2000306@sun.com>
Looks sane but your mailer ate the patch (line wrap monster got it)
Can you resend as an attachment ?
next prev parent reply other threads:[~2003-04-28 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 21:27 problem with a cobalt RaQ550 system and DMA (Serverworks OSB4 in impossible state) Olivier Bornet
2003-04-23 22:21 ` Alan Cox
2003-04-23 23:29 ` Olivier Bornet
2003-04-24 8:00 ` Olivier Bornet
2003-04-24 21:51 ` problem with Serverworks CSB5 IDE Duncan Laurie
2003-04-24 23:52 ` Duncan Laurie
2003-04-25 11:00 ` Alan Cox
2003-04-25 16:39 ` Duncan Laurie
2003-04-25 15:42 ` Alan Cox
2003-04-25 18:52 ` Duncan Laurie
2003-04-25 18:02 ` Alan Cox
2003-04-28 13:03 ` Alan Cox [this message]
2003-04-24 0:02 ` problem with a cobalt RaQ550 system and DMA (Serverworks OSB4 in impossible state) Duncan Laurie
2003-04-24 7:55 ` Olivier Bornet
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=1051535033.16809.15.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=duncan@sun.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;
as well as URLs for NNTP newsgroup(s).