diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2010-08-06 11:02:31 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2010-08-06 11:02:31 -0700 |
| commit | c513b67e68787eceafeede32bcd0edbee45c0006 (patch) | |
| tree | 91affc9a29a20b339b3c88ae3ee1e99eba49dc2b /drivers/base | |
| parent | 90c8327cad5d7c2d5d7d3e761d17af1925474107 (diff) | |
| download | kernel_samsung_tuna-c513b67e68787eceafeede32bcd0edbee45c0006.zip kernel_samsung_tuna-c513b67e68787eceafeede32bcd0edbee45c0006.tar.gz kernel_samsung_tuna-c513b67e68787eceafeede32bcd0edbee45c0006.tar.bz2 | |
pci: fix type warnings in intr_remapping.c
Commit 69309a059075 ("x86, asm: Clean up and simplify set_64bit()")
sanitized the x86-64 types to set_64bit(), and incidentally resulted in
warnings like
drivers/pci/intr_remapping.c: In function 'modify_irte':
drivers/pci/intr_remapping.c:314: warning: passing argument 1 of 'set_64bit' from incompatible pointer type
arch/x86/include/asm/cmpxchg_64.h:6: note:expected 'volatile u64 *' but argument is of type 'long unsigned int *'
It turns out that the change to set_64bit() really does clean up things,
and the PCI intr_remapping.c file did a rather ugly cast in order to
avoid warnings with the previous set_64bit() type model.
Removing the ugly cast fixes the warning, and makes everybody happy and
expects a set_64bit() to take the logical "u64 *" argument.
Pointed-out-by: Peter Anvin <hpa@zytor.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/base')
0 files changed, 0 insertions, 0 deletions