From: Dan Carpenter <error27@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Anton Vorontsov <cbouatmailru@gmail.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch -next] power/gpio-charger: check for kzalloc() failure
Date: Mon, 20 Dec 2010 20:30:04 +0000 [thread overview]
Message-ID: <20101220203004.GB1936@bicker> (raw)
In-Reply-To: <4D0FB6E6.2060608@metafoo.de>
On Mon, Dec 20, 2010 at 09:04:54PM +0100, Lars-Peter Clausen wrote:
> This is now the 4th patch or so fixing this issue.
Haha. No one can resist the easy one liners. If I had had to kfree() a
single variable before returning then you can know for a fact I'd be too
lazy to fix it. :P
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Anton Vorontsov <cbouatmailru@gmail.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch -next] power/gpio-charger: check for kzalloc() failure
Date: Mon, 20 Dec 2010 23:30:04 +0300 [thread overview]
Message-ID: <20101220203004.GB1936@bicker> (raw)
In-Reply-To: <4D0FB6E6.2060608@metafoo.de>
On Mon, Dec 20, 2010 at 09:04:54PM +0100, Lars-Peter Clausen wrote:
> This is now the 4th patch or so fixing this issue.
Haha. No one can resist the easy one liners. If I had had to kfree() a
single variable before returning then you can know for a fact I'd be too
lazy to fix it. :P
regards,
dan carpenter
next prev parent reply other threads:[~2010-12-20 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 13:08 [patch -next] power/gpio-charger: check for kzalloc() failure Dan Carpenter
2010-12-20 13:08 ` Dan Carpenter
2010-12-20 20:04 ` Lars-Peter Clausen
2010-12-20 20:04 ` Lars-Peter Clausen
2010-12-20 20:30 ` Dan Carpenter [this message]
2010-12-20 20:30 ` Dan Carpenter
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=20101220203004.GB1936@bicker \
--to=error27@gmail.com \
--cc=cbouatmailru@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@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.