From: Chris Ball <cjb@laptop.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: blp@cs.stanford.edu, Venkatraman S <svenkatr@ti.com>,
linux-mmc@vger.kernel.org, linux-sparse@vger.kernel.org
Subject: Re: [PATCH 2/2] mmc: fix integer assignments to pointer
Date: Tue, 23 Aug 2011 14:28:42 -0400 [thread overview]
Message-ID: <m2mxf02d9h.fsf@bob.laptop.org> (raw)
In-Reply-To: <20110823181359.GB3418@leaf> (Josh Triplett's message of "Tue, 23 Aug 2011 11:13:59 -0700")
Hi,
On Tue, Aug 23 2011, Josh Triplett wrote:
> {} produces the same effect, as far as I know.
Yeah. I prefer {0}, because {} is a gcc-ism (the ANSI grammar demands
initializer-lists be non-empty) and is less readable for people who
haven't seen the idiom before and are wondering what's going on.
I'm still a little confused -- the {0} or memset(0, struct ..);
formations are used often in the kernel, even with pointers involved.
Is the warning (Wnon_pointer_null) run against the kernel by default,
or did Venkatraman add it manually? If default, is it catching bugs?
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-08-23 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 15:46 [PATCH 0/2] mmc: trivial patches to fix sparse warnings Venkatraman S
2011-08-23 15:46 ` [PATCH 1/2] mmc: queue: declare mmc_alloc_sg as static Venkatraman S
2011-08-23 15:46 ` [PATCH 2/2] mmc: fix integer assignments to pointer Venkatraman S
2011-08-23 16:31 ` Chris Ball
2011-08-23 16:56 ` Sam Ravnborg
2011-08-23 17:36 ` Chris Ball
2011-08-23 22:40 ` J Freyensee
2011-08-24 11:23 ` S, Venkatraman
2011-08-23 17:28 ` Josh Triplett
2011-08-23 18:04 ` Ben Pfaff
2011-08-23 18:13 ` Josh Triplett
2011-08-23 18:28 ` Chris Ball [this message]
2011-08-23 20:22 ` Sam Ravnborg
2011-08-23 20:38 ` Sam Ravnborg
2011-08-24 18:33 ` S, Venkatraman
2011-08-23 20:43 ` Ben Pfaff
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=m2mxf02d9h.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=blp@cs.stanford.edu \
--cc=josh@joshtriplett.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=svenkatr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox