linux-kernel - Re: [PATCH] acpi: add some missing section markers

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] [day] [month] [year] [list]

Message-ID: <20090218182015.GB26802@elte.hu>
Date:	Wed, 18 Feb 2009 19:20:15 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	"Brown, Len" <len.brown@...el.com>,
	Yinghai Lu <yinghai@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] acpi: add some missing section markers


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> Ingo Molnar wrote:
>> * Jeremy Fitzhardinge <jeremy@...p.org> wrote:
>>
>>   
>>> early_acpi_os_unmap_memory() is an __init function, and  
>>> acpi_os_unmap_memory() is allowed to access an __init function until 
>>> acpi_gbl_permanent_mmap is set up.
>>>
>>> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
>>>     
>>
>> Note, this is modified by tip:x86/acpi, so if Len applies it to the 
>> ACPI tree we'll generate conflicts. Since the problem itself has been 
>> generated by the 6 commits in tip:x86/acpi, if Len is fine with it i'd 
>> like to apply your fix there.
>
> Sorry, I'd forgotten what path those patches were taking; I 
> just blindly applied the "ACPI=Len" pattern.

That was the correct pattern to apply in any case, as it 
modifies drivers/acpi/.

	Ingo
--
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/