[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F31DC88AC@ORSMSX106.amr.corp.intel.com>
Date: Thu, 13 Feb 2014 23:34:45 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Zheng, Lv" <lv.zheng@...el.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"Brown, Len" <len.brown@...el.com>
CC: Lv Zheng <zetalog@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"Yu, Fenghua" <fenghua.yu@...el.com>
Subject: RE: [PATCH 2/2] ACPICA: acpidump: Remove translation protection on
integer types.
> All definitions are equal except ACPI_UINT64_MAX for CONFIG_IA64. It
> is changed from sizeof(unsigned long) to sizeof(unsigned long long).
> By investigation, 64bit Linux kernel build is LP64 compliant, i.e.,
> sizeof(long) and (pointer) are 64. As sizeof(unsigned long) equals to
> sizeof(unsigned long long) on IA64 platform where CONFIG_64BIT cannot be
> disabled, this change actually will not affect the value of
> ACPI_UINT64_MAX on IA64 platforms.
This all looks correct to me - it really shouldn't make any difference
to ia64 whether we use "long" or "long long" ... both are 8-byte entities.
The compiler would complain in some places if you mixed & matched
incorrectly (e.g. printk("val = %ld\n", val); will give a warning if val has
been switched from "long" to "long long" and the format would need
to change to "%lld"). But it looks like nothing like that happens as a
result of this patch. All my ia64 configs build with no new warnings.
Boots OK too.
-Tony
--
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