From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/2] Use dev_sysdata for ACPI and remove firmware_data
Date: Fri, 10 Nov 2006 14:49:44 +0900 [thread overview]
Message-ID: <20061110054944.GB9137@kroah.com> (raw)
In-Reply-To: <1163033916.28571.803.camel@localhost.localdomain>
On Thu, Nov 09, 2006 at 11:58:36AM +1100, Benjamin Herrenschmidt wrote:
> This patch changes ACPI to use the new dev_sysdata on x86 and x86_64 (is there
> any other arch using ACPI ?) to store it's acpi_handle. It also removes the
> firmware_data field from struct device as this was the only user.
Yeah! I've wanted to drop firmware_data for a while now :)
thanks,
gre k-h
next prev parent reply other threads:[~2006-11-10 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 0:58 [PATCH 2/2] Use dev_sysdata for ACPI and remove firmware_data Benjamin Herrenschmidt
2006-11-10 5:49 ` Greg KH [this message]
2006-11-14 5:43 ` Len Brown
2006-11-14 5:50 ` Benjamin Herrenschmidt
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=20061110054944.GB9137@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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