[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120722163058.GB13376@localhost>
Date: Mon, 23 Jul 2012 00:30:58 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Mel Gorman <mgorman@...e.de>
Cc: kernel-janitors@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: [next:akpm 129/309] net/core/sock.c:274:36: error: initializer
element is not constant
Hi Mel,
To be frank, I don't quite understand this build failure..
tree: next/akpm akpm
head: 37e2ad4953983527f7bdb6831bf478eedcc84082
commit: 799dc3a908b1df8b766c35aefc24c1b5356aa051 [129/309] netvm: allow skb allocation to use PFMEMALLOC reserves
config: parisc-defconfig (attached as .config)
All related error/warning messages:
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
vim +274 net/core/sock.c
271 int sysctl_optmem_max __read_mostly = sizeof(unsigned long)*(2*UIO_MAXIOV+512);
272 EXPORT_SYMBOL(sysctl_optmem_max);
273
> 274 struct static_key memalloc_socks = STATIC_KEY_INIT_FALSE;
275 EXPORT_SYMBOL_GPL(memalloc_socks);
276
277 /**
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@...ux.intel.com> Intel Corporation
View attachment ".config" of type "text/plain" (48564 bytes)
Powered by blists - more mailing lists