[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1543551.z8D9aYzdaQ@vostro.rjw.lan>
Date: Tue, 16 Feb 2016 20:29:05 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: linux-kernel@...r.kernel.org, Aaron Lu <aaron.lu@...el.com>,
Huang Ying <ying.huang@...el.com>,
Josh Triplett <josh@...htriplett.org>,
Len Brown <lenb@...nel.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
linux-acpi@...r.kernel.org
Subject: Re: [PATCH 0/3] acpi: remove modular references from non modular code
On Monday, February 15, 2016 12:27:48 AM Paul Gortmaker wrote:
> An audit of i386/x86_64 allmodconfig builds found these instances of
> non-modular ACPI code needlessly using the modular equivalents of
> their built-in counterparts.
>
> In fixing that, we get rid of some dead code, make the mandate of
> the remaining code more clear, and leave behind better examples
> for future ACPI code to copy/emulate.
>
> Two of them are trivial, in that there is no binary output change.
> The other has dead code removal so the binary output will be
> slightly smaller. We've done a direct mapping of module_init to
> device_initcall in each instance, so there is no initcall
> reordering risks here. Overall, in all cases, the runtime should
> be completely unchanged.
>
> Where others have deployed module_param() already, we have to
> leave it, because there is no equivalent builtin_param (not yet)
> and we have to remain compatible with existing bootarg users.
All three applied.
Thanks,
Rafael
Powered by blists - more mailing lists