From: Borislav Petkov <bp@amd64.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Borislav Petkov <bp@amd64.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Tony Luck <tony.luck@intel.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
EDAC devel <linux-edac@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Rename perf_event.c
Date: Tue, 3 May 2011 14:51:19 +0200 [thread overview]
Message-ID: <20110503125119.GC20241@aftab> (raw)
In-Reply-To: <20110503082234.GB6999@elte.hu>
On Tue, May 03, 2011 at 04:22:34AM -0400, Ingo Molnar wrote:
> Could you send a Git pull request against perf/core that does the
> obvious file movement and renaming? We can do that first step straight
> away and get the ball rolling.
Sure, here we go:
The following changes since commit ac0a3260f37b8616da8d33488ec94b94e6ae5b31:
Merge branch 'tip/perf/core' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace into perf/core (2011-05-01 19:11:42 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git perf-event-rename
Borislav Petkov (1):
perf: Start the restructuring
kernel/Makefile | 5 +++--
kernel/events/Makefile | 5 +++++
kernel/{perf_event.c => events/core.c} | 0
3 files changed, 8 insertions(+), 2 deletions(-)
create mode 100644 kernel/events/Makefile
rename kernel/{perf_event.c => events/core.c} (100%)
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-05-03 12:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 17:34 [PATCH 0/4] RAS daemon: kernel part Borislav Petkov
2011-05-02 17:34 ` [PATCH 1/4] perf: Start the restructuring Borislav Petkov
2011-05-02 17:34 ` [PATCH 2/4] perf: Add persistent event facilities Borislav Petkov
2011-05-03 6:40 ` Ingo Molnar
2011-05-03 6:48 ` Ingo Molnar
2011-05-03 7:12 ` Borislav Petkov
2011-05-03 8:22 ` Ingo Molnar
2011-05-03 12:51 ` Borislav Petkov [this message]
2011-05-03 12:59 ` Frederic Weisbecker
2011-05-03 13:30 ` Borislav Petkov
2011-05-03 14:26 ` Borislav Petkov
2011-05-02 17:34 ` [PATCH 3/4] x86, mce: Add persistent MCE event Borislav Petkov
2011-05-03 6:44 ` Ingo Molnar
2011-05-03 7:18 ` Borislav Petkov
2011-05-03 8:27 ` Ingo Molnar
2011-05-03 15:14 ` Joe Perches
2011-05-03 15:22 ` Borislav Petkov
2011-05-03 15:32 ` Joe Perches
2011-05-03 15:34 ` Steven Rostedt
2011-05-03 15:42 ` Borislav Petkov
2011-05-02 17:34 ` [PATCH 4/4] x86, mce: Have MCE persistent event off by default for now Borislav Petkov
2011-05-03 6:45 ` Ingo Molnar
2011-05-03 7:23 ` Borislav Petkov
2011-05-03 8:17 ` Ingo Molnar
2011-05-03 17:17 ` Luck, Tony
2011-05-03 19:52 ` Borislav Petkov
2011-05-03 19:56 ` Ingo Molnar
2011-05-04 6:58 ` Ingo Molnar
2011-05-04 21:40 ` Luck, Tony
2011-05-05 1:34 ` Arnaldo Carvalho de Melo
2011-05-05 6:39 ` Ingo Molnar
2011-05-05 7:17 ` Borislav Petkov
2011-05-05 7:33 ` Ingo Molnar
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=20110503125119.GC20241@aftab \
--to=bp@amd64.org \
--cc=acme@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tony.luck@intel.com \
/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