From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Matt Tolentino <metolent@snoqualmie.dp.intel.com>
Cc: akpm@osdl.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, Matt_Domsch@dell.com,
matthew.e.tolentino@intel.com
Subject: Re: [patch 1/3] efivars driver update and move
Date: Thu, 22 Apr 2004 16:46:59 +0000 [thread overview]
Message-ID: <200404221046.59541.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200404221732.i3MHWJcc023373@snoqualmie.dp.intel.com>
On Thursday 22 April 2004 11:32 am, Matt Tolentino wrote:
> I broke up the efivars driver update patch I had sent out
> quite a while ago into several smaller patches. This
> includes several fixes and suggestions that were pointed
> out. The patches are broken down as follows:
>
> 1 - remove all traces of efivars from arch/ia64/
> 2 - add new sysfs based efivars driver into
> drivers/firmware with accompanying Kconfig/Makefile
> changes to make it fully functional for ia64 again.
> 3 - cleans up x86 references to the /proc version of
> the efivars driver.
I like these changes.
I did notice that the new drivers/.../efivars.c is not identical to
the old arch/ia64/kernel/efivars.c (the hints to emacs were removed).
I like the emacs hint removal, but didn't review patch for any other
differences.
Any plans to consolidate other bits from efi.c? There are a number
of things there that look like they could be shared:
is_available_memory()
efi_init()
(mostly)
efi_initialize_iomem_resources()
(i386 only today, but I think we'd like it for ia64 also)
efi_mem_type()
efi_mem_attributes()
(the i386 versions look slightly buggy in that they
assume a fixed descriptor size, so old kernels won't
work with new firmware that adds stuff to the descriptor)
Bjorn
next prev parent reply other threads:[~2004-04-22 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 15:51 [patch 1/3] efivars driver update and move Matt Tolentino
2004-04-22 16:46 ` Bjorn Helgaas [this message]
2004-04-22 17:14 ` Tolentino, Matthew E
2004-04-22 17:20 ` Bjorn Helgaas
2004-04-29 19:50 ` Alex Williamson
2004-04-29 21:19 ` Matt Domsch
2004-04-29 22:08 ` Alex Williamson
2004-04-23 22:29 ` Matt Domsch
2004-04-24 3:41 ` Matt Domsch
2004-04-26 18:57 ` Matt Domsch
2004-04-26 19:30 ` Matt Tolentino
2004-04-30 0:09 ` Matt Tolentino
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=200404221046.59541.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=metolent@snoqualmie.dp.intel.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