From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH] efivars move to drivers/efi, efibootmgr-0.5.0-test1
Date: Mon, 15 Sep 2003 22:14:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106366423525055@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106313960719815@msgid-missing>
>>>>> On Tue, 9 Sep 2003 15:03:38 -0500 (CDT), Matt Domsch <Matt_Domsch@dell.com> said:
Matt> Matt Tolentino posted a patch a couple weeks ago moving
Matt> arch/ia64/efivars.c to drivers/efi and converting it to use
Matt> sysfs. He did a pretty good job, but there were some things I
Matt> wanted cleaned up with that. He's out of the office for a few
Matt> days being a new father (Congrats!), so I took a stab at
Matt> finishing the job.
Matt> First, the move and conversion (appended):
Matt> http://domsch.com/linux/ia64/linux-2.6.0-test5-efivars-sysfs-20030909.patch
Matt> http://domsch.com/linux/ia64/linux-2.6.0-test5-efivars-sysfs-20030909.patch.asc
Matt> arch/ia64/Kconfig | 10
Matt> arch/ia64/defconfig | 1
Matt> arch/ia64/kernel/Makefile | 1
Matt> arch/ia64/kernel/efi.c | 19 -
Matt> arch/ia64/kernel/efivars.c | 508 --------------------------------
Matt> drivers/Makefile | 1
Matt> drivers/efi/Kconfig | 23 +
Matt> drivers/efi/Makefile | 4
Matt> drivers/efi/efivars.c | 695 +++++++++++++++++++++++++++++++++++++++++++++
Matt> include/linux/efi.h | 1
Matt> 10 files changed, 726 insertions, 537 deletions
I'm fine with the ia64-specific changes, but I can't apply them
until/unless the generic changes are in. Perhaps the best thing to do
would be to send the entire patch to Linus (with my approval for the
ia64-specific changes). That way, all files get updated "atomically".
--david
prev parent reply other threads:[~2003-09-15 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 20:03 [RFC][PATCH] efivars move to drivers/efi, efibootmgr-0.5.0-test1 Matt Domsch
2003-09-15 22:14 ` David Mosberger [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=marc-linux-ia64-106366423525055@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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