From: Dan Carpenter <error27@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: smatch: leds: potential null deref
Date: Wed, 07 Apr 2010 09:44:42 +0000 [thread overview]
Message-ID: <20100407094442.GI5157@bicker> (raw)
In-Reply-To: <20100407091850.GB5157@bicker>
On Wed, Apr 07, 2010 at 12:18:50PM +0300, Dan Carpenter wrote:
> Hello,
>
> Smatch complains about a potential null dereference but I don't know how
> to fix it. Could you take a look?
>
Sorry I should have mentioned that I'll be offline for probably a week.
So don't hurry on my account. :)
regards,
dan carpenter
next prev parent reply other threads:[~2010-04-07 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 9:18 smatch: leds: potential null deref Dan Carpenter
2010-04-07 9:44 ` Dan Carpenter [this message]
2010-04-09 10:14 ` Haojian Zhuang
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=20100407094442.GI5157@bicker \
--to=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
/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.