diff options
author | Mel Gorman <mgorman@suse.de> | 2012-07-23 15:16:19 +0400 |
---|---|---|
committer | James Bottomley <JBottomley@Parallels.com> | 2012-07-25 09:08:46 +0400 |
commit | bba3d8c3b3c0f2123be5bc687d1cddc13437c923 (patch) | |
tree | 190b3d251a506e0258796f88492d8e1c5e2ad609 /fs/btrfs/ctree.c | |
parent | bdc0077af574800d24318b6945cf2344e8dbb050 (diff) | |
download | linux-bba3d8c3b3c0f2123be5bc687d1cddc13437c923.tar.xz |
[PARISC] Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts
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>
Cc: <stable@vger.kernel.org>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
Diffstat (limited to 'fs/btrfs/ctree.c')
0 files changed, 0 insertions, 0 deletions