From: David Sterba <dsterba@suse.cz>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: Gui Hecheng <guihc.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 5/5] btrfs-progs:free strdup()s that are not freed
Date: Mon, 9 Sep 2013 16:40:21 +0200 [thread overview]
Message-ID: <20130909144021.GP32382@twin.jikos.cz> (raw)
In-Reply-To: <52282E7B.6010309@giantdisaster.de>
On Thu, Sep 05, 2013 at 09:10:51AM +0200, Stefan Behrens wrote:
> Just noticed that you had already sent a V2 with the things fixed that I
> have commented, but you sent the 5/5 as a 1/5 and added the changelog
> v1->v2 "none" which made it difficult to recognize :). But maybe David
> Sterba is smart enough when he picks up the patches.
I watch out for updates and replace the patches with the latest version.
V3 of "free strdup()s that are not freed" has been merged.
Thanks for the pointer anyway.
david
prev parent reply other threads:[~2013-09-09 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 2:38 [PATCH 0/5] Memory leaks amended Gui Hecheng
2013-09-05 2:38 ` [PATCH 1/5] btrfs-progs:free local variable buf upon unsuccessful returns Gui Hecheng
2013-09-05 2:38 ` [PATCH 2/5] btrfs-progs:local variable memory freed Gui Hecheng
2013-09-09 14:18 ` David Sterba
2013-09-09 14:22 ` David Sterba
2013-09-05 2:38 ` [PATCH 3/5] btrfs-progs: missing tree-freeing statements added Gui Hecheng
2013-09-05 2:38 ` [PATCH 4/5] btrfs-progs:free the local list pending_list in btrfs_scan_one_dir Gui Hecheng
2013-09-05 2:38 ` [PATCH 5/5] btrfs-progs:free strdup()s that are not freed Gui Hecheng
2013-09-05 7:00 ` Stefan Behrens
2013-09-05 7:10 ` Stefan Behrens
2013-09-05 8:08 ` Gui Hecheng
2013-09-05 8:10 ` Wang Shilong
2013-09-09 14:40 ` David Sterba [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=20130909144021.GP32382@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=guihc.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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).