From: David Woodhouse <dwmw2@infradead.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] Use check_legacy_ioport() for ISAPnP
Date: Wed, 27 Sep 2006 13:49:45 +0100 [thread overview]
Message-ID: <1159361385.3309.118.camel@pmac.infradead.org> (raw)
In-Reply-To: <20060927081838.GA5984@aepfle.de>
On Wed, 2006-09-27 at 10:18 +0200, Olaf Hering wrote:
> Isnt that fixed by my other patch which was merged into -mm today?
Hm, wasn't aware of that.
/me looks...
No, your patch seems to change pnpbios, not isapnp. Which is odd, since
pnpbios is x86-only anyway.
And did you fix the case of PCI parallel ports? We only want to do the
check_legacy_ioport() thing for the 'default' built-in ports, not for
all ports.
--
dwmw2
next prev parent reply other threads:[~2006-09-27 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 7:18 [PATCH] Use check_legacy_ioport() for ISAPnP David Woodhouse
2006-09-27 8:18 ` Olaf Hering
2006-09-27 12:49 ` David Woodhouse [this message]
2006-09-27 13:05 ` Olaf Hering
2006-10-02 9:38 ` Olaf Hering
2006-10-02 9:42 ` David Woodhouse
2006-10-02 10:00 ` Olaf Hering
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=1159361385.3309.118.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olaf@aepfle.de \
--cc=paulus@samba.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).