public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: robert.richter@amd•com (Robert Richter)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] oprofile, arm: proper release resources on failure
Date: Wed, 29 Sep 2010 16:52:25 +0200	[thread overview]
Message-ID: <20100929145225.GJ13563@erda.amd.com> (raw)

Will,

the patch below fixes a resource leak I found during code review. Can
you please review and test it (I don't have an ARM environment for
this available). If you are fine with the change, please ack. I want
to send it upstream via tip/perf/urgent.

Though you reworked the code already, parts of the fix are still valid
for latest oprofile code in oprofile/core.

Ingo,

if Will agrees with it, please apply it directly to tip/perf/urgent.

Thanks,

-Robert

--

             reply	other threads:[~2010-09-29 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 14:52 Robert Richter [this message]
2010-09-29 15:39 ` [PATCH] oprofile, arm: proper release resources on failure Will Deacon
2010-09-29 16:50   ` Robert Richter
2010-09-29 16:59     ` Robert Richter
2010-09-29 17:32       ` Will Deacon
2010-09-29 17:39         ` Robert Richter
  -- strict thread matches above, loose matches on Subject: below --
2010-09-29 14:03 Robert Richter

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=20100929145225.GJ13563@erda.amd.com \
    --to=robert.richter@amd$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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