public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"oprofile-list@lists.sourceforge.net" 
	<oprofile-list@lists.sourceforge.net>
Subject: Re: [GIT PULL] oprofile fixes for v3.0
Date: Thu, 9 Jun 2011 09:02:38 +0200	[thread overview]
Message-ID: <20110609070237.GO20052@erda.amd.com> (raw)
In-Reply-To: <20110608140631.GA30752@elte.hu>

On 08.06.11 10:06:31, Ingo Molnar wrote:
> 
> * Robert Richter <robert.richter@amd.com> wrote:
> 
> > Ingo,
> > 
> > please pull oprofile fixes for v3.0 (tip/perf/urgent):
> > 
> >  git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git urgent
> > 
> > Thanks,
> > 
> > -Robert
> > 
> > 
> > The following changes since commit d7ebe75b065a7c2d58ffc12f9d2e00d5ea4e71eb:
> > 
> >   perf: Fix comments in include/linux/perf_event.h (2011-06-04 12:31:14 +0200)
> > 
> > are available in the git repository at:
> >   git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git urgent
> > 
> > Robert Richter (4):
> >       oprofile, x86: Add comments to IBS LVT offset initialization

Ingo,

it seems you pulled (86dd7909c2c4ae3f219a9233bf0f095b05632ecf) from

 cbf74cea070fa1f705de4712e25d9e56ae6543c7 (oprofile, x86: Add comments to IBS LVT offset initialization)

These ones are still missing:

> >       oprofile: Free potentially owned tasks in case of errors
> >       oprofile: Fix locking dependency in sync_start()
> >       oprofile, dcookies: Fix possible circular locking dependency

But oprofile/urgent is

 fe47ae7f53e179d2ef6771024feb000cbb86640f (oprofile, dcookies: Fix possible circular locking dependency)

Is this intended? Maybe a korg git sync issue?

Thanks,

-Robert

> > 
> >  arch/x86/kernel/apic/apic.c      |    3 ++-
> >  arch/x86/oprofile/op_model_amd.c |   13 +++++++++----
> >  drivers/oprofile/buffer_sync.c   |   21 +++++++++++----------
> >  fs/dcookies.c                    |    3 +++
> >  4 files changed, 25 insertions(+), 15 deletions(-)
> 
> Pulled, thanks a lot Robert!
> 
> 	Ingo
> 

-- 
Advanced Micro Devices, Inc.
Operating System Research Center


  reply	other threads:[~2011-06-09  7:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 16:46 [PATCH 0/3] oprofile fixes for 3.0 Robert Richter
2011-05-31 16:46 ` [PATCH 1/3] oprofile: Free potentially owned tasks in case of errors Robert Richter
2011-05-31 16:46 ` [PATCH 2/3] oprofile: Fix locking dependency in sync_start() Robert Richter
2011-05-31 16:46 ` [PATCH 3/3] oprofile, dcookies: Fix possible circular locking Robert Richter
2011-06-08 12:53 ` [GIT PULL] oprofile fixes for v3.0 Robert Richter
2011-06-08 14:06   ` Ingo Molnar
2011-06-09  7:02     ` Robert Richter [this message]
2011-06-09  7:15       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2011-06-21 12:52 Robert Richter
2011-06-21 13:03 ` Ingo Molnar
2011-06-21 17:54   ` Robert Richter
2011-06-21 20:18     ` Ingo Molnar
2011-06-22 13:50       ` 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=20110609070237.GO20052@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oprofile-list@lists.sourceforge.net \
    /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