From: Jeff Garzik <jgarzik@pobox.com>
To: Tobias Reinhard <tracer@robotech.de>
Cc: linux-ide@vger.kernel.org
Subject: Re: Problem with concurrent SATA-Writes
Date: Wed, 01 Jun 2005 13:33:40 -0400 [thread overview]
Message-ID: <429DF174.2000002@pobox.com> (raw)
In-Reply-To: <429DECA2.6020609@robotech.de>
Tobias Reinhard wrote:
> Hello Jeff, hello to the linux-ide-list!
>
> I already posted this to the lkml, but unfortunately I got no usefull
> answer. I think the problem is related to the SIL-Driver so maybe you
> are the right person to contact - or someone at the linux-ide-list...
>
> If you need any other informations or logs please tell me. I really want
> to use these discs.
Yes, I think this is the third time I've read your email. You can stop
posting it now.
Sometimes we just don't have time to read and respond to every support
request. If you absolutely require support, please use a paid support
channel like SuSE or Red Hat.
Jeff
next prev parent reply other threads:[~2005-06-01 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 17:13 Problem with concurrent SATA-Writes Tobias Reinhard
2005-06-01 17:33 ` Jeff Garzik [this message]
2005-06-01 22:40 ` Tobias Reinhard
2005-06-02 21:57 ` Jeff Garzik
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=429DF174.2000002@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=tracer@robotech.de \
/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).