From: Len Brown <len.brown@intel.com>
To: Greg KH <greg@kroah.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/2] Use dev_sysdata for ACPI and remove firmware_data
Date: Tue, 14 Nov 2006 00:43:30 -0500 [thread overview]
Message-ID: <200611140043.30714.len.brown@intel.com> (raw)
In-Reply-To: <20061110054944.GB9137@kroah.com>
On Friday 10 November 2006 00:49, Greg KH wrote:
> 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 :)
device.firmware_data was born when we went to link Linux devices
and ACPI devices using device.platform_data and found it was already used.
You recommended we create a new field to avoid the conflict, and
IIR the discussion suggested that eventually device.platform_data use
would get cleaned up and the fields could perhaps some day be combined.
I don't know if we are any closer to that day, before or after this change.
However, I'm fine with Ben's re-name -- it changes no functionality on ACPI-enabled
systems while potentially deleting an unused pointer/dev on other architectures.
Please ship his patch #2 along with patch #1 that it depends on.
Acked-by: Len Brown <len.brown@intel.com>
thanks
-Len
next prev parent reply other threads:[~2006-11-14 5:40 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
2006-11-14 5:43 ` Len Brown [this message]
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=200611140043.30714.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--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 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.