All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: Mel Gorman <mgorman@suse.de>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	kernel-janitors@vger.kernel.org,
	Kyle McMartin <kyle@parisc-linux.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [next:akpm 129/309] net/core/sock.c:274:36: error: initializer element is not constant
Date: Tue, 24 Jul 2012 07:48:44 +0000	[thread overview]
Message-ID: <20120724074844.GA9519@localhost> (raw)
In-Reply-To: <BLU0-SMTP2254F8872DDE5FA6035CDE97DD0@phx.gbl>

> It would be easier to see what's happening with preprocessed source.

Here is the line in sock.i:

struct static_key memalloc_socks = ((struct static_key) { .enabled = ((atomic_t) { (0) }) });

Thanks,
Fengguang

WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: Mel Gorman <mgorman@suse.de>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	kernel-janitors@vger.kernel.org,
	Kyle McMartin <kyle@parisc-linux.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [next:akpm 129/309] net/core/sock.c:274:36: error: initializer element is not constant
Date: Tue, 24 Jul 2012 15:48:44 +0800	[thread overview]
Message-ID: <20120724074844.GA9519@localhost> (raw)
In-Reply-To: <BLU0-SMTP2254F8872DDE5FA6035CDE97DD0@phx.gbl>

> It would be easier to see what's happening with preprocessed source.

Here is the line in sock.i:

struct static_key memalloc_socks = ((struct static_key) { .enabled = ((atomic_t) { (0) }) });

Thanks,
Fengguang

  reply	other threads:[~2012-07-24  7:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-22 16:30 [next:akpm 129/309] net/core/sock.c:274:36: error: initializer element is not constant Fengguang Wu
2012-07-22 16:30 ` Fengguang Wu
2012-07-23 11:16 ` Mel Gorman
2012-07-23 11:16   ` Mel Gorman
2012-07-23 11:20   ` James Bottomley
2012-07-23 11:20     ` James Bottomley
2012-07-23 11:42     ` Mel Gorman
2012-07-23 11:42       ` Mel Gorman
2012-07-23 12:29       ` Fengguang Wu
2012-07-23 12:29         ` Fengguang Wu
2012-07-23 15:13         ` John David Anglin
2012-07-23 15:13           ` John David Anglin
2012-07-24  7:48           ` Fengguang Wu [this message]
2012-07-24  7:48             ` Fengguang Wu
2012-07-24 21:08             ` John David Anglin
2012-07-24 21:08               ` John David Anglin
2012-07-25  5:10               ` James Bottomley
2012-07-25  5:10                 ` James Bottomley
2012-07-26 17:06                 ` Tony Luck
2012-07-26 17:06                   ` Tony Luck
2012-08-02 15:02                   ` Fengguang Wu
2012-08-02 15:02                     ` Fengguang Wu
2012-08-12  1:33                     ` Michael Cree
2012-08-12  1:33                       ` Michael Cree
2012-08-12  2:10                       ` Fengguang Wu
2012-08-12  2:10                         ` Fengguang Wu
2012-08-12  2:42                         ` Michael Cree
2012-08-12  2:42                           ` Michael Cree
2012-08-12 13:00                           ` John David Anglin
2012-08-12 13:00                             ` John David Anglin
2012-08-12  2:14                       ` [PATCH] [ALPHA] Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts Fengguang Wu
2012-08-12  2:14                         ` Fengguang Wu
2012-08-15 22:03                         ` Andrew Morton
2012-08-15 22:03                           ` Andrew Morton
2012-07-25  8:27               ` [next:akpm 129/309] net/core/sock.c:274:36: error: initializer element is not constant Mel Gorman
2012-07-25  8:27                 ` Mel Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120724074844.GA9519@localhost \
    --to=fengguang.wu@intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.anglin@bell.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kyle@parisc-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mgorman@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.