From: Andi Kleen <ak@suse.de>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: tom.l.nguyen@intel.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] PCI MSI Kconfig consolidation
Date: Tue, 13 Apr 2004 21:29:37 +0000 [thread overview]
Message-ID: <20040413232937.7d907a71.ak@suse.de> (raw)
In-Reply-To: <200404131408.17248.bjorn.helgaas@hp.com>
On Tue, 13 Apr 2004 14:08:17 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>
> In fact, I think there's a whole lot more architecture-specific
> knowledge that has leaked across into drivers/pci/msi.[ch]. For
Yes. Far too lot. Even for the relatively small x86<->x86-64 differences.
That was the reason I disabled it for x86-64 initially ....
[hoping that someone with MSI hardware will fix and reenable it]
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: tom.l.nguyen@intel.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] PCI MSI Kconfig consolidation
Date: Tue, 13 Apr 2004 23:29:37 +0200 [thread overview]
Message-ID: <20040413232937.7d907a71.ak@suse.de> (raw)
In-Reply-To: <200404131408.17248.bjorn.helgaas@hp.com>
On Tue, 13 Apr 2004 14:08:17 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>
> In fact, I think there's a whole lot more architecture-specific
> knowledge that has leaked across into drivers/pci/msi.[ch]. For
Yes. Far too lot. Even for the relatively small x86<->x86-64 differences.
That was the reason I disabled it for x86-64 initially ....
[hoping that someone with MSI hardware will fix and reenable it]
-Andi
next prev parent reply other threads:[~2004-04-13 21:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 16:41 [PATCH] PCI MSI Kconfig consolidation Bjorn Helgaas
2004-04-13 16:41 ` Bjorn Helgaas
2004-04-13 18:37 ` Andi Kleen
2004-04-13 18:37 ` Andi Kleen
2004-04-13 19:16 ` Nguyen, Tom L
2004-04-13 19:16 ` Nguyen, Tom L
2004-04-13 20:08 ` Bjorn Helgaas
2004-04-13 20:08 ` Bjorn Helgaas
2004-04-13 21:29 ` Andi Kleen [this message]
2004-04-13 21:29 ` Andi Kleen
2004-04-13 20:09 ` Grant Grundler
2004-04-13 20:09 ` Grant Grundler
2004-04-13 21:54 ` Nguyen, Tom L
2004-04-13 21:54 ` Nguyen, Tom L
2004-04-13 21:57 ` Nguyen, Tom L
2004-04-13 21:57 ` Nguyen, Tom L
2004-04-15 20:49 ` Nguyen, Tom L
2004-04-15 20:49 ` Nguyen, Tom L
2004-04-16 0:41 ` Bjorn Helgaas
2004-04-16 0:41 ` Bjorn Helgaas
2004-04-16 15:15 ` Nguyen, Tom L
2004-04-16 15:15 ` Nguyen, Tom L
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=20040413232937.7d907a71.ak@suse.de \
--to=ak@suse.de \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.l.nguyen@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.