diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2016-02-22 22:58:34 +0100 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2016-02-23 17:17:20 -0800 |
| commit | c45442055dfdeb265cc20c9eeaa9fd11a75fbf51 (patch) | |
| tree | ec9c304ceb425db702af367028cb9861684fe30e /kernel/resource.c | |
| parent | 93f834df9c2d4e362dfdc4b05daa0a4e18814836 (diff) | |
| download | linux-stable-c45442055dfdeb265cc20c9eeaa9fd11a75fbf51.tar.gz linux-stable-c45442055dfdeb265cc20c9eeaa9fd11a75fbf51.tar.bz2 linux-stable-c45442055dfdeb265cc20c9eeaa9fd11a75fbf51.zip | |
nvdimm: use 'u64' for pfn flags
A recent bugfix changed pfn_t to always be 64-bit wide, but did not
change the code in pmem.c, which is now broken on 32-bit architectures
as reported by gcc:
In file included from ../drivers/nvdimm/pmem.c:28:0:
drivers/nvdimm/pmem.c: In function 'pmem_alloc':
include/linux/pfn_t.h:15:17: error: large integer implicitly truncated to unsigned type [-Werror=overflow]
#define PFN_DEV (1ULL << (BITS_PER_LONG_LONG - 3))
This changes the intermediate pfn_flags in struct pmem_device to
be 64 bit wide as well, so they can store the flags correctly.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Fixes: db78c22230d0 ("mm: fix pfn_t vs highmem")
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'kernel/resource.c')
0 files changed, 0 insertions, 0 deletions