From: Marcin Dalecki <dalecki@evision.ag>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: lkml <linux-kernel@vger.kernel.org>,
axboe@suse.de, torvalds@transmeta.com
Subject: Re: IDE lockups with 2.5.28...
Date: Fri, 26 Jul 2002 12:31:30 +0200 [thread overview]
Message-ID: <3D412502.1000406@evision.ag> (raw)
In-Reply-To: 32AE2E2034@vcnet.vc.cvut.cz
Petr Vandrovec wrote:
> On 26 Jul 02 at 12:00, Petr Vandrovec wrote:
>
>
>>P.S.: I did not saw IDE 105. Does it exist?
>
>
> Ah, found that while reading rest of LKLM. Why so secret name
> "Re: Linux 2.5.28" ?
Just becouse I abuse my reply button as address book :-).
Not really intentionall.
next prev parent reply other threads:[~2002-07-26 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 10:30 IDE lockups with 2.5.28 Petr Vandrovec
2002-07-26 10:31 ` Marcin Dalecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-26 10:46 Petr Vandrovec
2002-07-26 10:00 Petr Vandrovec
2002-07-26 10:30 ` Marcin Dalecki
2002-07-25 17:22 Petr Vandrovec
2002-07-26 2:09 ` Marcin Dalecki
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=3D412502.1000406@evision.ag \
--to=dalecki@evision.ag \
--cc=VANDROVE@vc.cvut.cz \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=torvalds@transmeta.com \
/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