From: Matt Fleming <matt@codeblueprint.co.uk> To: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>, Tony Luck <tony.luck@gmail.com>, Matt Fleming <matt@codeblueprint.co.uk> Subject: [PATCH 0/2] efi: Delete global 'memmap' variable Date: Mon, 11 Apr 2016 14:03:27 +0100 [thread overview] Message-ID: <1460379809-18490-1-git-send-email-matt@codeblueprint.co.uk> (raw) Ard's recent EFI memory attributes table patches caused ia64 build failures due to the use of the global 'memmap' EFI memory map object, which doesn't exist on ia64. That failure prompted me to dig out these two patches that delete 'memmap' once and for all and replace all occurrences with 'efi.memmap'. And because all call sites are now using 'efi.memmap' for_each_efi_memory_desc() can implicitly use that object instead of requiring it to be passed as an argument. Matt Fleming (2): efi: Iterate over efi->memmap in for_each_efi_memory_desc efi: Remove global 'memmap' arch/x86/platform/efi/efi.c | 125 ++++++++++++------------- arch/x86/platform/efi/efi_64.c | 10 +- arch/x86/platform/efi/quirks.c | 10 +- drivers/firmware/efi/arm-init.c | 20 ++-- drivers/firmware/efi/arm-runtime.c | 15 +-- drivers/firmware/efi/efi.c | 8 +- drivers/firmware/efi/fake_mem.c | 43 +++++---- drivers/firmware/efi/libstub/efi-stub-helper.c | 6 +- include/linux/efi.h | 14 ++- 9 files changed, 121 insertions(+), 130 deletions(-) -- 2.7.3
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org> To: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>, Tony Luck <tony.luck-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org> Subject: [PATCH 0/2] efi: Delete global 'memmap' variable Date: Mon, 11 Apr 2016 14:03:27 +0100 [thread overview] Message-ID: <1460379809-18490-1-git-send-email-matt@codeblueprint.co.uk> (raw) Ard's recent EFI memory attributes table patches caused ia64 build failures due to the use of the global 'memmap' EFI memory map object, which doesn't exist on ia64. That failure prompted me to dig out these two patches that delete 'memmap' once and for all and replace all occurrences with 'efi.memmap'. And because all call sites are now using 'efi.memmap' for_each_efi_memory_desc() can implicitly use that object instead of requiring it to be passed as an argument. Matt Fleming (2): efi: Iterate over efi->memmap in for_each_efi_memory_desc efi: Remove global 'memmap' arch/x86/platform/efi/efi.c | 125 ++++++++++++------------- arch/x86/platform/efi/efi_64.c | 10 +- arch/x86/platform/efi/quirks.c | 10 +- drivers/firmware/efi/arm-init.c | 20 ++-- drivers/firmware/efi/arm-runtime.c | 15 +-- drivers/firmware/efi/efi.c | 8 +- drivers/firmware/efi/fake_mem.c | 43 +++++---- drivers/firmware/efi/libstub/efi-stub-helper.c | 6 +- include/linux/efi.h | 14 ++- 9 files changed, 121 insertions(+), 130 deletions(-) -- 2.7.3
next reply other threads:[~2016-04-11 13:03 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-11 13:03 Matt Fleming [this message] 2016-04-11 13:03 ` [PATCH 0/2] efi: Delete global 'memmap' variable Matt Fleming 2016-04-11 13:03 ` [PATCH 1/2] efi: Iterate over efi->memmap in for_each_efi_memory_desc Matt Fleming 2016-04-11 13:03 ` Matt Fleming 2016-04-11 13:24 ` kbuild test robot 2016-04-11 13:24 ` kbuild test robot 2016-04-11 13:27 ` kbuild test robot 2016-04-11 13:27 ` kbuild test robot 2016-04-11 13:03 ` [PATCH 2/2] efi: Remove global 'memmap' Matt Fleming 2016-04-11 13:03 ` Matt Fleming 2016-04-11 13:17 ` Ard Biesheuvel 2016-04-12 20:01 ` Matt Fleming 2016-04-12 20:01 ` Matt Fleming 2016-04-13 8:12 ` Ard Biesheuvel 2016-04-13 8:12 ` Ard Biesheuvel 2016-04-13 10:24 ` Matt Fleming 2016-04-13 10:24 ` Matt Fleming
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=1460379809-18490-1-git-send-email-matt@codeblueprint.co.uk \ --to=matt@codeblueprint.co.uk \ --cc=ard.biesheuvel@linaro.org \ --cc=linux-efi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=tony.luck@gmail.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: linkBe 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.