From: Mike Frysinger <vapier@gentoo.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
patches@opensource.wolfsonmicro.com,
device-drivers-devel@blackfin.uclinux.org,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [Device-drivers-devel] [PATCH] ASoC: Fix NULL vs. 0 warning in SSM2602
Date: Tue, 10 May 2011 18:48:58 -0400 [thread overview]
Message-ID: <BANLkTi=btxtcGeSZAQVAcPxS6VKTAeEqWg@mail.gmail.com> (raw)
In-Reply-To: <1305064982-26328-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Tue, May 10, 2011 at 18:03, Mark Brown wrote:
> sparse complains if 0 is used as a NULL pointer constant.
Acked-by: Mike Frysinger <vapier@gentoo.org>
-mike
next prev parent reply other threads:[~2011-05-10 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 22:03 [PATCH] ASoC: Fix NULL vs. 0 warning in SSM2602 Mark Brown
2011-05-10 22:48 ` Mike Frysinger [this message]
2011-05-11 13:12 ` Liam Girdwood
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='BANLkTi=btxtcGeSZAQVAcPxS6VKTAeEqWg@mail.gmail.com' \
--to=vapier@gentoo.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=lars@metafoo.de \
--cc=lrg@slimlogic.co.uk \
--cc=patches@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).