From: David Gibson <david@gibson.dropbear.id.au>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Ettl <ettl.martin@gmx.de>
Subject: Re: [PATCH] scripts/dtc: Fix a resource leak
Date: Sat, 3 Jul 2010 11:56:49 +1000 [thread overview]
Message-ID: <20100703015649.GD27004@yookeroo> (raw)
In-Reply-To: <1278071534-9820-1-git-send-email-mmarek@suse.cz>
On Fri, Jul 02, 2010 at 01:52:14PM +0200, Michal Marek wrote:
> From: Martin Ettl <ettl.martin@gmx.de>
>
> during a check of the current git head of the linux kernel with the
> static code analysis tool cppcheck
> (http://sourceforge.net/apps/mediawiki/cppcheck/index.php?title=Main_Page)
> the tool discovered a resource leak in linux-2.6/scripts/dtc/fstree.c.
>
> Please refer the attached patch, that fixes the issue.
I'll submit a patch for this to upstream dtc.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2010-07-03 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 11:52 [PATCH] scripts/dtc: Fix a resource leak Michal Marek
2010-07-03 1:56 ` David Gibson [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=20100703015649.GD27004@yookeroo \
--to=david@gibson.dropbear.id.au \
--cc=ettl.martin@gmx.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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