public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH 1/2] efi: merge x86 and ia64 code
Date: Wed, 13 Jul 2011 20:58:27 +0100	[thread overview]
Message-ID: <20110713195827.GA9910@srcf.ucam.org> (raw)
In-Reply-To: <4E1DEAA2.80208@zytor.com>

On Wed, Jul 13, 2011 at 11:57:38AM -0700, H. Peter Anvin wrote:

> I get a build error on x86-32:
> 
> /home/hpa/kernel/linux-2.6-tip.efi/arch/x86/platform/efi/efi_32.c:43:
> error: conflicting types for ‘efi_call_phys_prelog’
> /home/hpa/kernel/linux-2.6-tip.efi/arch/x86/include/asm/efi.h:73: note:
> previous declaration of ‘efi_call_phys_prelog’ was here
> /home/hpa/kernel/linux-2.6-tip.efi/arch/x86/platform/efi/efi_32.c:85:
> error: conflicting types for ‘efi_call_phys_epilog’
> /home/hpa/kernel/linux-2.6-tip.efi/arch/x86/include/asm/efi.h:74: note:
> previous declaration of ‘efi_call_phys_epilog’ was here
> make[5]: *** [arch/x86/platform/efi/efi_32.o] Error 1

Oops.

It's sadly much easier to test IA64 than it is to test 32-bit EFI 
booting, but this one should at least build and link.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2011-07-13 19:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 20:24 [PATCH 1/2] efi: merge x86 and ia64 code Matthew Garrett
2011-07-12 20:24 ` [PATCH 2/2] MAINTAINERS: Add a maintainer for EFI Matthew Garrett
2011-07-12 20:40   ` Joe Perches
2011-07-13 18:57 ` [PATCH 1/2] efi: merge x86 and ia64 code H. Peter Anvin
2011-07-13 19:58   ` Matthew Garrett [this message]
2011-07-13 19:59   ` [PATCH V2 " Matthew Garrett
2011-07-13 19:59     ` [PATCH V2 2/2] MAINTAINERS: Add a maintainer for EFI Matthew Garrett

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=20110713195827.GA9910@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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