From: Martin Dalecki <dalecki@evision-ventures.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Anthony Spinillo <tspinillo@linuxmail.org>, linux-kernel@vger.kernel.org
Subject: Re: INTEL 845G Chipset IDE Quandry
Date: Mon, 03 Jun 2002 11:28:31 +0200 [thread overview]
Message-ID: <3CFB36BF.2040605@evision-ventures.com> (raw)
In-Reply-To: <20020602101628.4230.qmail@linuxmail.org> <3CFA73C3.9010902@evision-ventures.com> <20020602233043.A11698@ucw.cz> <3CFAF4A0.5010702@evision-ventures.com> <20020603104747.C13158@ucw.cz> <3CFB231E.7010806@evision-ventures.com> <20020603113753.B13637@ucw.cz>
Vojtech Pavlik wrote:
> The PCI code under normal circumstances can fix the allocation problems
> by itself (without any special quirks code), but in this case it simply
> fails. Do you still have the original e-mail with the dmesg? I'd like to
> look at that again ...
No becouse It wasn't directed at me.
next prev parent reply other threads:[~2002-06-03 10:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 10:16 INTEL 845G Chipset IDE Quandry Anthony Spinillo
2002-06-02 19:36 ` Martin Dalecki
2002-06-02 21:30 ` Vojtech Pavlik
2002-06-03 1:13 ` Alan Cox
2002-06-03 8:43 ` Vojtech Pavlik
2002-06-03 11:49 ` Kjartan Maraas
2002-06-03 10:10 ` Andre Hedrick
2002-06-03 4:46 ` Martin Dalecki
2002-06-03 8:47 ` Vojtech Pavlik
2002-06-03 8:04 ` Martin Dalecki
2002-06-03 9:37 ` Vojtech Pavlik
2002-06-03 9:28 ` Martin Dalecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 23:35 Anthony Spinillo
2002-06-03 1:04 Anthony Spinillo
2002-06-03 9:22 ` Vojtech Pavlik
2002-06-02 1:58 Bartlomiej Zolnierkiewicz
2002-06-02 6:01 ` Martin Dalecki
2002-06-03 8:59 ` Andre Hedrick
2002-06-01 21:43 Anthony Spinillo
2002-06-01 11:03 Anthony Spinillo
2002-06-01 12:40 ` Alan Cox
2002-06-01 20:13 ` Andre Hedrick
2002-06-01 19:53 ` Andre Hedrick
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=3CFB36BF.2040605@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tspinillo@linuxmail.org \
--cc=vojtech@suse.cz \
/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