From: Jon Loeliger Subject: Re: dtc: Audit and fix valgrind errors Date: Wed, 24 Feb 2010 08:57:22 -0600 Message-ID: References: <20100224112919.GA31576@yookeroo> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-reply-to: <20100224112919.GA31576@yookeroo> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: David Gibson Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org List-Id: devicetree@vger.kernel.org > The somewhat embarrasing bug in the first version of my previous patch > would have been detected by valgrind. Thus reminded, I've run the > testsuite under valgrind and fixed any errors I found. This turned > out to be just some uninitialized buffers in test programs. The > fragments of uninitialized data aren't particularly important, but we > might as well squash the valgrind warnings, so that future valgrind > errors will stand out. > > Signed-off-by: David Gibson Applied. Thanks, jdl