From: Sachin Kamat <sachin.kamat@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
broonie@opensource.wolfsonmicro.com, swarren@nvidia.com,
lgirdwood@gmail.com
Subject: Re: [PATCH 4/5] ASoC: tegra: Use NULL instead of 0 for pointers
Date: Tue, 22 Jan 2013 10:31:09 +0530 [thread overview]
Message-ID: <CAK9yfHyGmQYh5jp2sVySSXcXmm9HPaYxLM67CSF5MF5Dbb7rVA@mail.gmail.com> (raw)
In-Reply-To: <50FD779E.5010800@wwwdotorg.org>
On 21 January 2013 22:45, Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 01/21/2013 02:29 AM, Sachin Kamat wrote:
>> Fixes the following sparse warnings:
>> sound/soc/tegra/tegra30_ahub.c:583:16: warning:
>> Using plain integer as NULL pointer
>> sound/soc/tegra/tegra30_ahub.c:600:16: warning:
>> Using plain integer as NULL pointer
>
> Out of curiosity, which compiler is this with; I've never seen this warning.
This is actually a sparse warning which you can see if you build the
kernel with C=1 (or C=2) option as below:
make C=1 [targets] Check all c source with $CHECK (sparse by default)
make C=2 [targets] Force check of all c source with $CHECK
--
With warm regards,
Sachin
next prev parent reply other threads:[~2013-01-22 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 9:29 [PATCH 0/5] ASoC: tegra: Some fixes in codec files Sachin Kamat
2013-01-21 9:29 ` [PATCH 1/5] ASoC: tegra_wm9712: Remove __devinitconst attribute Sachin Kamat
2013-01-21 9:29 ` [PATCH 2/5] ASoC: tegra20_ac97: " Sachin Kamat
2013-01-21 9:29 ` [PATCH 3/5] ASoC: tegra: Make 'ahub_auxdata' static Sachin Kamat
2013-01-21 17:16 ` Stephen Warren
2013-01-22 4:56 ` Sachin Kamat
2013-01-21 9:29 ` [PATCH 4/5] ASoC: tegra: Use NULL instead of 0 for pointers Sachin Kamat
2013-01-21 17:15 ` Stephen Warren
2013-01-22 5:01 ` Sachin Kamat [this message]
2013-01-21 9:29 ` [PATCH 5/5] ASoC: tegra: Staticize some functions in tegra30_i2s.c Sachin Kamat
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=CAK9yfHyGmQYh5jp2sVySSXcXmm9HPaYxLM67CSF5MF5Dbb7rVA@mail.gmail.com \
--to=sachin.kamat@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=tiwai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).