summaryrefslogtreecommitdiff
path: root/arch/alpha/oprofile
diff options
context:
space:
mode:
authorMel Gorman <mgorman@suse.de>2012-08-19 14:41:03 +1200
committerLinus Torvalds <torvalds@linux-foundation.org>2012-08-19 08:41:19 -0700
commit67a806d9499353fabd5b5ff07337f3aa88a1c3ba (patch)
tree4ab86067b178abb2d99a79c5e2ecced476830a60 /arch/alpha/oprofile
parent0be421862b857e61964435ffcaa7499cf77a5e5a (diff)
Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts
The following build error occurred during an alpha build: 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. Cc: <stable@vger.kernel.org> Signed-off-by: Mel Gorman <mgorman@suse.de> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com> Signed-off-by: Michael Cree <mcree@orcon.net.nz> Acked-by: Matt Turner <mattst88@gmail.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/alpha/oprofile')
0 files changed, 0 insertions, 0 deletions