From: Matt_Domsch@Dell.com
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] move asm-ia64/efi.h to linux/efi.h ?
Date: Tue, 13 Aug 2002 22:38:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905936@msgid-missing> (raw)
David, any further thoughts on moving include/asm-ia64/efi.h to linux/efi.h?
Now that EFI GUID Partition Tables are part of the stock 2.4 and 2.5 kernel
series, and can be (and will be!) used on x86 platforms too, several people
have commented on l-k this week that it doesn't make sense to keep it in
asm-ia64. I agree. There's also no ia64-specific code in there.
I'd be happy to work up a patch to move it if there was a chance it would be
accepted and submitted to Marcelo and Linus.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer, Architect
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
#1 US Linux Server provider for 2001 and Q1/2002! (IDC May 2002)
next reply other threads:[~2002-08-13 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 22:38 Matt_Domsch [this message]
2002-08-13 22:51 ` [Linux-ia64] move asm-ia64/efi.h to linux/efi.h ? David Mosberger
2002-08-14 19:42 ` Matt_Domsch
2002-08-14 20:33 ` Matt_Domsch
2002-08-15 16:55 ` Matt_Domsch
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-105590701905936@msgid-missing \
--to=matt_domsch@dell.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