From: Zach Brown <zab@zabbo.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Pavel Roskin <proski@gnu.org>, Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Patch to make ymfpci legacy address 16 bits
Date: Wed, 9 May 2001 19:53:07 -0400 [thread overview]
Message-ID: <20010509195307.G30257@erasmus.off.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0105091627440.5113-100000@fonzie.nine.com> <3AF9B1BF.A6BCCCE2@mandrakesoft.com>
In-Reply-To: <3AF9B1BF.A6BCCCE2@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, May 09, 2001 at 05:08:15PM -0400
On Wed, May 09, 2001 at 05:08:15PM -0400, Jeff Garzik wrote:
> Why does maestro.c not use my suggestion? Because it doesn't use struct
> pci_driver.
I finally found an able hacker with maestro hardware with power
management. He not only fixed the nasty pm races that were causing
channel corruption, but he seems willing to move it towards the proper
pci_driver APIs as well.
So don't worry Jeff, we'll fix the evil maestro.c driver yet :) :)
- z
next prev parent reply other threads:[~2001-05-09 23:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 20:17 Patch to make ymfpci legacy address 16 bits Pavel Roskin
2001-05-09 20:23 ` Jeff Garzik
2001-05-09 20:52 ` Pavel Roskin
2001-05-09 21:08 ` Jeff Garzik
2001-05-09 23:43 ` Pavel Roskin
2001-05-09 23:53 ` Zach Brown [this message]
2001-05-10 2:53 ` Albert D. Cahalan
2001-05-10 7:28 ` Question: Status of USAGI/FreeSWAN? Dax Kelson
2001-05-11 2:52 ` Mike Fedyk
2001-05-10 11:54 ` Patch to make ymfpci legacy address 16 bits mirabilos
-- strict thread matches above, loose matches on Subject: below --
2001-05-09 0:37 Pete Zaitcev
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=20010509195307.G30257@erasmus.off.net \
--to=zab@zabbo.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.org \
--cc=zaitcev@redhat.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