[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87oaqdy13n.fsf@rasmusvillemoes.dk>
Date: Mon, 05 Jan 2015 11:26:52 +0100
From: Rasmus Villemoes <linux@...musvillemoes.dk>
To: "Zheng\, Lv" <lv.zheng@...el.com>
Cc: "linux-acpi\@vger.kernel.org" <linux-acpi@...r.kernel.org>,
"devel\@acpica.org" <devel@...ica.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] ACPICA: Remove use of __DATE__ macro
On Mon, Jan 05 2015, "Zheng, Lv" <lv.zheng@...el.com> wrote:
> Hi,
>
>> From: Rasmus Villemoes [mailto:linux@...musvillemoes.dk]
>> Sent: Friday, December 12, 2014 6:51 PM
>> To: Zheng, Lv
>> Cc: Rasmus Villemoes; linux-acpi@...r.kernel.org; devel@...ica.org; linux-kernel@...r.kernel.org
>> Subject: [PATCH 3/3] ACPICA: Remove use of __DATE__ macro
>>
>> The macro __DATE__ and friends is not allowed in the kernel. Also,
>> including the build time in output doesn't seem to provide any value.
>>
>
> Could you confirm that it is not useful even for the user tools?
> Please perform the following commands in the kernel source tree
> 1. stay in tools folder
> 2. type "make acpi"
> 3. type "./power/acpi/acpidump -v"
>
Yeah, it's part of the output, but for what reason? What can userspace
possibly use that information for? I can see some utility in printing a
version number, since that may tell something about the features
present or absent. The compilation date, on the other hand, seems
completely useless. Different distros may ship different versions which
happened to be compiled on the same day, or older versions compiled later.
Note that -Werror=date-time was added to the kernel's default build
flags in fe7c36c7bde12. It doesn't currently show because tools/ uses
its own flags, and the ACPI_COMMON_SIGNON macro is not used within the
kernel.
Rasmus
--
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/
Powered by blists - more mailing lists