diff options
author | Mel Gorman <mgorman@suse.de> | 2012-07-23 12:16:19 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-09-14 10:00:51 -0700 |
commit | 2b6007fbac1484f788ffffd545d916c10d1fe2e2 (patch) | |
tree | 936712432d3b6bc98d7846c6b75771b67066f20d /include | |
parent | 839b995a17f8f16528e6e01a6c2b65fbc2ce8733 (diff) | |
download | kernel_samsung_tuna-2b6007fbac1484f788ffffd545d916c10d1fe2e2.zip kernel_samsung_tuna-2b6007fbac1484f788ffffd545d916c10d1fe2e2.tar.gz kernel_samsung_tuna-2b6007fbac1484f788ffffd545d916c10d1fe2e2.tar.bz2 |
PARISC: Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts
commit bba3d8c3b3c0f2123be5bc687d1cddc13437c923 upstream.
The following build error occured during a parisc build with
swap-over-NFS patches applied.
net/core/sock.c:274:36: error: initializer element is not constant
net/core/sock.c:274:36: error: (near initialization for 'memalloc_socks')
net/core/sock.c:274:36: error: initializer element is not constant
Dave Anglin says:
> Here is the line in sock.i:
>
> struct static_key memalloc_socks = ((struct static_key) { .enabled =
> ((atomic_t) { (0) }) });
The above line contains two compound literals. It also uses a designated
initializer to initialize the field enabled. A compound literal is not a
constant expression.
The location of the above statement isn't fully clear, but if a compound
literal occurs outside the body of a function, the initializer list must
consist of constant expressions.
Reported-by: Fengguang Wu <fengguang.wu@intel.com>
Signed-off-by: Mel Gorman <mgorman@suse.de>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions