All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Hammond, John" <john.hammond@intel.com>
Cc: Bruce Korb <bruce.korb@gmail.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"Dilger, Andreas" <andreas.dilger@intel.com>,
	Kees Cook <keescook@chromium.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Drokin, Oleg" <oleg.drokin@intel.com>,
	Vitaly Fertman <vitaly_fertman@xyratex.com>,
	"Liu, Emoly" <emoly.liu@intel.com>,
	"Faccini, Bruno" <bruno.faccini@intel.com>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH] staging: lustre: ldlm: use designated initializers
Date: Tue, 20 Dec 2016 22:07:51 +0300	[thread overview]
Message-ID: <20161220190750.GO8176@mwanda> (raw)
In-Reply-To: <C6D48C5819337145905EDC9DB164E69728D44FEC@fmsmsx120.amr.corp.intel.com>

On Tue, Dec 20, 2016 at 02:57:17PM +0000, Hammond, John wrote:
> "{ NULL }" is valid ISO C, but unfortunately "{}" is not.

In the kernel we don't care.  We use lots of GCC extensions.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Hammond, John" <john.hammond@intel.com>
Cc: Bruce Korb <bruce.korb@gmail.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"Dilger, Andreas" <andreas.dilger@intel.com>,
	Kees Cook <keescook@chromium.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Drokin, Oleg" <oleg.drokin@intel.com>,
	Vitaly Fertman <vitaly_fertman@xyratex.com>,
	"Liu, Emoly" <emoly.liu@intel.com>,
	"Faccini, Bruno" <bruno.faccini@intel.com>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] [PATCH] staging: lustre: ldlm: use designated initializers
Date: Tue, 20 Dec 2016 22:07:51 +0300	[thread overview]
Message-ID: <20161220190750.GO8176@mwanda> (raw)
In-Reply-To: <C6D48C5819337145905EDC9DB164E69728D44FEC@fmsmsx120.amr.corp.intel.com>

On Tue, Dec 20, 2016 at 02:57:17PM +0000, Hammond, John wrote:
> "{ NULL }" is valid ISO C, but unfortunately "{}" is not.

In the kernel we don't care.  We use lots of GCC extensions.

regards,
dan carpenter

  parent reply	other threads:[~2016-12-20 19:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-17  1:00 [PATCH] staging: lustre: ldlm: use designated initializers Kees Cook
2016-12-17  1:00 ` [lustre-devel] " Kees Cook
2016-12-19 16:22 ` James Simmons
2016-12-19 16:22   ` [lustre-devel] " James Simmons
2016-12-19 16:47   ` Bruce Korb
2016-12-19 16:48     ` [lustre-devel] " Bruce Korb
2016-12-19 17:12     ` James Simmons
2016-12-19 17:12       ` [lustre-devel] " James Simmons
2016-12-20  7:10     ` Dan Carpenter
2016-12-20  7:10       ` [lustre-devel] " Dan Carpenter
2016-12-20 14:57       ` Hammond, John
2016-12-20 14:57         ` [lustre-devel] " Hammond, John
2016-12-20 16:47         ` Bruce Korb
2016-12-20 16:48           ` [lustre-devel] " Bruce Korb
2016-12-20 18:52           ` Dan Carpenter
2016-12-20 18:52             ` [lustre-devel] " Dan Carpenter
2016-12-20 19:07         ` Dan Carpenter [this message]
2016-12-20 19:07           ` Dan Carpenter
2016-12-20 19:46           ` Kees Cook
2016-12-20 19:46             ` [lustre-devel] " Kees Cook
2016-12-19 16:50   ` Patrick Farrell
2016-12-19 17:11     ` James Simmons
2016-12-19 17:11       ` James Simmons
2016-12-20 10:40   ` Dan Carpenter
2016-12-20 10:40     ` [lustre-devel] " Dan Carpenter
2016-12-20 17:29 ` Designated initializers, struct randomization and addressing? Joe Perches
2016-12-20 17:29   ` [lustre-devel] " Joe Perches
2017-01-03 23:47   ` Kees Cook
2017-01-03 23:55     ` Bruce Korb
2017-01-04  0:13       ` Kees Cook
2017-01-04  6:27     ` Julia Lawall
2017-01-04  6:35       ` Kees Cook
2017-01-04 16:55         ` Stephen Hemminger
2017-01-04 17:37           ` Julia Lawall
2017-01-04 22:30           ` Kees Cook

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=20161220190750.GO8176@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=andreas.dilger@intel.com \
    --cc=bruce.korb@gmail.com \
    --cc=bruno.faccini@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=emoly.liu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.hammond@intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=oleg.drokin@intel.com \
    --cc=vitaly_fertman@xyratex.com \
    /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.