linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: OProfile for linux-next
Date: Thu, 30 Jul 2009 14:07:38 +0200	[thread overview]
Message-ID: <20090730120738.GA24694@erda.amd.com> (raw)

Stephen,

please add following tree to linux-next:

 git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git for-next

This is the oprofile master branch containing all changes for the next
merge window.

The general way of sending oprofile to linux-next is via tip. So, this
will be a temporary solution until Ingo will be back.

Thanks,

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com

             reply	other threads:[~2009-07-30 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 12:07 Robert Richter [this message]
2009-07-30 23:25 ` OProfile for linux-next Stephen Rothwell

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=20090730120738.GA24694@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).