From: Rajesh Shah <rajesh.shah@intel.com>
To: Greg KH <greg@kroah.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Kristen Accardi <kristen.c.accardi@intel.com>,
rajesh.shah@intel.com, gregkh@suse.de, ak@suse.de,
len.brown@intel.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz,
acpi-devel@lists.sourceforge.net
Subject: Re: [patch 2/2] i386/x86_64: collect host bridge resources v2
Date: Thu, 30 Jun 2005 17:33:25 -0700 [thread overview]
Message-ID: <20050630173322.A8366@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050630160506.GD6828@kroah.com>; from greg@kroah.com on Thu, Jun 30, 2005 at 09:05:06AM -0700
On Thu, Jun 30, 2005 at 09:05:06AM -0700, Greg KH wrote:
> >
> > Probably there is a conflict between e820 map and root bus ranges
> > reported by ACPI. I think that it would be better to just drop
> > gregkh-pci-pci-collect-host-bridge-resources-02.patch rather than
> > try to fix it, at least until such conflicts can be resolved in
> > a sane way.
>
> Ok, I'll drop it. Any objections to me doing this?
>
OK with me. I actually think there are interactions between other
patches that may also be the cause for some of the problems
reported recently. However, I'm mostly out for the next 2
weeks, and will look at this more closely when I return.
Rajesh
prev parent reply other threads:[~2005-07-01 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 22:41 [patch 0/2] Collecting host bridge resources - take 2 rajesh.shah
2005-06-02 22:41 ` [patch 1/2] Increase the number of PCI bus resources rajesh.shah
2005-06-02 22:41 ` [patch 2/2] i386/x86_64: collect host bridge resources v2 rajesh.shah
2005-06-28 11:51 ` Ivan Kokshaysky
2005-06-28 18:21 ` Kristen Accardi
2005-06-28 20:03 ` Ivan Kokshaysky
2005-06-30 16:05 ` Greg KH
2005-07-01 0:33 ` Rajesh Shah [this message]
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=20050630173322.A8366@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=ink@jurassic.park.msu.ru \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.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