From: Andrew Morton <akpm@osdl.org>
To: Greg KH <greg@kroah.com>
Cc: John Keller <jpk@sgi.com>,
linux-ia64@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [Pcihpd-discuss] [PATCH 1/3] - Altix: Add initial ACPI IO
Date: Thu, 05 Oct 2006 00:36:33 +0000 [thread overview]
Message-ID: <20061004173633.c193eafd.akpm@osdl.org> (raw)
In-Reply-To: <20061004225649.GB14395@kroah.com>
On Wed, 4 Oct 2006 15:56:49 -0700
Greg KH <greg@kroah.com> wrote:
> On Wed, Oct 04, 2006 at 04:49:25PM -0500, John Keller wrote:
> > First phase in introducing ACPI support to SN.
> > In this phase, when running with an ACPI capable PROM,
> > the DSDT will define the root busses and all SN nodes
> > (SGIHUB, SGITIO). An ACPI bus driver will be registered
> > for the node devices, with the acpi_pci_root_driver being
> > used for the root busses. An ACPI vendor descriptor is
> > now used to pass platform specific information for both
> > nodes and busses, eliminating the need for the current
> > SAL calls. Also, with ACPI support, SN fixup code is no longer
> > needed to initiate the PCI bus scans, as the acpi_pci_root_driver
> > does that.
>
> How do these three patches differ from the ones I added to my tree
> yesterday?
A bunch of other stuff got merged out of order this morning and broke your
tree. I asked John for a rediff. Check your inbox ;)
> > Resend #2 - resync with TOT
>
> "TOT"?
tip-of-tree.
next prev parent reply other threads:[~2006-10-05 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 16:01 [PATCH 1/3] - Altix: Add initial ACPI IO support John Keller
2006-09-22 14:51 ` John Keller
2006-10-01 7:15 ` Andrew Morton
2006-10-02 19:02 ` John Keller
2006-10-03 14:56 ` John Keller
2006-10-04 21:49 ` John Keller
2006-10-04 22:56 ` [Pcihpd-discuss] " Greg KH
2006-10-05 0:36 ` Andrew Morton [this message]
2006-10-05 13:10 ` John Keller
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=20061004173633.c193eafd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jpk@sgi.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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