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 19:39:47 +0200 [thread overview]
Message-ID: <20100929173947.GS13563@erda.amd.com> (raw)
In-Reply-To: <1285781578.22669.4.camel@e102144-lin.cambridge.arm.com>
On 29.09.10 13:32:58, Will Deacon wrote:
> Robert,
>
> On Wed, 2010-09-29 at 17:59 +0100, Robert Richter wrote:
> > On 29.09.10 18:50:27, Robert Richter wrote:
> >
> > > > Hmm, these three hunks conflict with the patches I posted last
> > > > month to fix the resource allocation and freeing. Can't we
> > > > merge those patches instead? I have versions against -rc6 here:
> > >
> > > Yes, these patches are also in my oprofile/core branch and its changes
> > > conflict, but are scheduled for the next merge window. This fix is for
> > > urgent and for 2.6.36. We will then merge back rc7 or 2.6.36 to
> > > oprofile/core and solve the conflicts. But if you don't have something
> > > else for -rc7/.36 that conflicts, this should be ok.
> >
> > So, it would be ok then to test only this fix on -rc6 without your
> > other patches.
> >
>
> Gotcha - this is a minimal fixup for -stable which we'll tackle properly
> in the merge window with the stuff in oprofile/core. In that case I'm
> happy for this to go upstream now:
>
> Acked-by: Will Deacon <will.deacon@arm.com>
>
>
> I also built an -rc6 kernel with this change on top and OProfile worked
> happily across module loads/unloads.
>
> As for oprofile/core; will you handle the conflicts there or do I need
> to resend my previous patches?
Yes, I will merge it after it went upstream and let you know.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
WARNING: multiple messages have this Message-ID (diff)
From: Robert Richter <robert.richter@amd.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] oprofile, arm: proper release resources on failure
Date: Wed, 29 Sep 2010 19:39:47 +0200 [thread overview]
Message-ID: <20100929173947.GS13563@erda.amd.com> (raw)
In-Reply-To: <1285781578.22669.4.camel@e102144-lin.cambridge.arm.com>
On 29.09.10 13:32:58, Will Deacon wrote:
> Robert,
>
> On Wed, 2010-09-29 at 17:59 +0100, Robert Richter wrote:
> > On 29.09.10 18:50:27, Robert Richter wrote:
> >
> > > > Hmm, these three hunks conflict with the patches I posted last
> > > > month to fix the resource allocation and freeing. Can't we
> > > > merge those patches instead? I have versions against -rc6 here:
> > >
> > > Yes, these patches are also in my oprofile/core branch and its changes
> > > conflict, but are scheduled for the next merge window. This fix is for
> > > urgent and for 2.6.36. We will then merge back rc7 or 2.6.36 to
> > > oprofile/core and solve the conflicts. But if you don't have something
> > > else for -rc7/.36 that conflicts, this should be ok.
> >
> > So, it would be ok then to test only this fix on -rc6 without your
> > other patches.
> >
>
> Gotcha - this is a minimal fixup for -stable which we'll tackle properly
> in the merge window with the stuff in oprofile/core. In that case I'm
> happy for this to go upstream now:
>
> Acked-by: Will Deacon <will.deacon@arm.com>
>
>
> I also built an -rc6 kernel with this change on top and OProfile worked
> happily across module loads/unloads.
>
> As for oprofile/core; will you handle the conflicts there or do I need
> to resend my previous patches?
Yes, I will merge it after it went upstream and let you know.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
next prev parent reply other threads:[~2010-09-29 17:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 14:52 [PATCH] oprofile, arm: proper release resources on failure Robert Richter
2010-09-29 14:52 ` Robert Richter
2010-09-29 15:39 ` Will Deacon
2010-09-29 15:39 ` Will Deacon
2010-09-29 16:50 ` Robert Richter
2010-09-29 16:50 ` Robert Richter
2010-09-29 16:59 ` Robert Richter
2010-09-29 16:59 ` Robert Richter
2010-09-29 17:32 ` Will Deacon
2010-09-29 17:32 ` Will Deacon
2010-09-29 17:39 ` Robert Richter [this message]
2010-09-29 17:39 ` Robert Richter
2010-10-04 20:24 ` [tip:perf/urgent] oprofile, ARM: Release " tip-bot for Robert Richter
2010-10-16 16:32 ` [tip:perf/core] " tip-bot for Robert Richter
-- strict thread matches above, loose matches on Subject: below --
2010-09-29 14:03 [PATCH] oprofile, arm: proper release " 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=20100929173947.GS13563@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.