From: Dan Carpenter <dan.carpenter@oracle.com>
To: Peter Huewe <PeterHuewe@gmx.de>
Cc: Rupesh Gujare <rupesh.gujare@atmel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Kernel Janitors <kernel-janitors@vger.kernel.org>
Subject: Re: Clang Analyzer was Re: [PATCH 3/7 v2] staging/ozwpan: Fix NULL vs zero in ozeltbuf.c (sparse war
Date: Fri, 15 Feb 2013 16:11:02 +0000 [thread overview]
Message-ID: <20130215161102.GK6853@mwanda> (raw)
In-Reply-To: <201302151657.14726.PeterHuewe@gmx.de>
Are you using this version of clang?:
http://git.linuxfoundation.org/llvmlinux.git/
regards,
dan carpenter
next prev parent reply other threads:[~2013-02-15 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130215084517.GB6802@mwanda>
[not found] ` <1360938148-19225-3-git-send-email-peterhuewe@gmx.de>
[not found] ` <20130215145226.GI6853@mwanda>
2013-02-15 15:57 ` Clang Analyzer was Re: [PATCH 3/7 v2] staging/ozwpan: Fix NULL vs zero in ozeltbuf.c (sparse warning Peter Huewe
2013-02-15 16:11 ` Dan Carpenter [this message]
2013-02-15 16:34 ` Clang Analyzer was Re: [PATCH 3/7 v2] staging/ozwpan: Fix NULL vs zero in ozeltbuf.c (sparse war Peter Hüwe
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=20130215161102.GK6853@mwanda \
--to=dan.carpenter@oracle.com \
--cc=PeterHuewe@gmx.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rupesh.gujare@atmel.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