From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: [For review] [PATCH] Check all kmalloc(), etc, functions for success
Date: Wed, 28 Apr 2010 07:44:33 -0400 [thread overview]
Message-ID: <4BD81FA1.5010309@csamuel.org> (raw)
In-Reply-To: <4BD61CAA.7090206@csamuel.org>
On 26/04/10 19:07, Chris Samuel wrote:
> Please review the patch and let me know whether I'm on the
> right track or not! Just be gentle with me, I'm jetlagged. :-)
Did this patch make it out OK ?
If so, any thoughts if my thinking is OK on how to address this ?
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
prev parent reply other threads:[~2010-04-28 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 23:07 [For review] [PATCH] Check all kmalloc(), etc, functions for success Chris Samuel
2010-04-28 11:44 ` Chris Samuel [this message]
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=4BD81FA1.5010309@csamuel.org \
--to=chris@csamuel.org \
--cc=linux-btrfs@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 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).