linux-kernel - Re: [PATCH 2/6] X86 ACPI: Introduce x86 arch specific arch_reserve_mem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201209251712.17678.trenn@suse.de>
Date:	Tue, 25 Sep 2012 17:12:17 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	hpa@...or.com
Cc:	lenb@...nel.org, initramfs@...r.kernel.org, robert.moore@...el.com,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	yinghai@...nel.org
Subject: Re: [PATCH 2/6] X86 ACPI: Introduce x86 arch specific arch_reserve_mem_area() for e820 handling

On Tuesday, September 25, 2012 04:55:57 PM Thomas Renninger wrote:
> This is needed for ACPI table overriding via initrd. Beside reserving
> memblocks, X86 also requires to flag the memory area to E820_RESERVED or
> E820_ACPI in the e820 mappings to be able to io(re)map it later.
...

> index 4f2a762..bf6a0ad 100644
> --- a/include/linux/acpi.h
> +++ b/include/linux/acpi.h
> @@ -430,4 +430,13 @@ acpi_status acpi_os_prepare_sleep(u8 sleep_state,
>  #define acpi_os_set_prepare_sleep(func, pm1a_ctrl, pm1b_ctrl) do { } while (0)
>  #endif
>  
> +#if CONFIG_X86
> +void arch_reserve_mem_area(acpi_physical_address addr, size_t size);
> +#else
> +static inline void void arch_reserve_mem_area(acpi_physical_address addr,

Argh: ...void void... 
I made sure every single patch compiles, so that no typo slips
in, I haven't compiled it on an other arch and there ... a typo
slipped in.

Can this get manually fixed?
Tell me and I can also resend.

    Thomas


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/