From: Andi Kleen <ak@suse.de>
To: Aaron Durbin <adurbin@google.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, matthias.lenk@amd.com
Subject: Re: [PATCH] i386/x86_64: Insert HPET firmware resource after PCI enumeration has completed
Date: Fri, 6 Jul 2007 12:59:36 +0200 [thread overview]
Message-ID: <200707061259.36526.ak@suse.de> (raw)
In-Reply-To: <20070705222724.GA12537@google.com>
On Friday 06 July 2007 00:27:24 Aaron Durbin wrote:
>
> Insert HPET resources after pci probing has been completed in order to avoid
> resource conflicts with PCI resource reservation. With this change the
> HPET firmware resources will be identified, but it should also not cause
> issues when the HPET address falls on a BAR in a PCI device, and the PCI
> enumeration cannot reserve the resources.
But what advantage does it have when it's already reserved by PCI?
That's only a cosmetic change, isn't it? A lot of code for cosmetics.
-Andi
next prev parent reply other threads:[~2007-07-06 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 22:27 [PATCH] i386/x86_64: Insert HPET firmware resource after PCI enumeration has completed Aaron Durbin
2007-07-06 10:59 ` Andi Kleen [this message]
2007-07-06 11:09 ` Matthias Lenk
2007-07-09 14:07 ` Matthias Lenk
2007-07-06 12:45 ` Aaron Durbin
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=200707061259.36526.ak@suse.de \
--to=ak@suse.de \
--cc=adurbin@google.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.lenk@amd.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