From: Ingo Molnar <mingo@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
Lance Ortiz <lance.ortiz@hp.com>
Subject: Re: [GIT PULL] Use perf/event tracing to report PCI Express advanced errors
Date: Thu, 24 Jan 2013 14:49:45 +0100 [thread overview]
Message-ID: <20130124134945.GB9715@gmail.com> (raw)
In-Reply-To: <50e744c134281a8f8@agluck-desk.sc.intel.com>
* Luck, Tony <tony.luck@intel.com> wrote:
> The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
>
> Linux 3.8-rc2 (2013-01-02 18:13:21 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/please-pull-aer-trace
>
> for you to fetch changes up to 2cced2d95961acd318e9395578a60ee424d9db80:
>
> aerdrv: Cleanup log output for AER (2013-01-03 14:35:41 -0800)
>
> ----------------------------------------------------------------
> Use perf/event tracing to report PCI Express advanced errors.
>
> ----------------------------------------------------------------
> Lance Ortiz (3):
> aerdrv: Trace Event for PCI Express Advanced Error Reporting
> aerdrv: Enhanced AER logging
> aerdrv: Cleanup log output for AER
>
> drivers/acpi/apei/cper.c | 19 ++++++--
> drivers/pci/pcie/aer/aerdrv_errprint.c | 63 ++++++++++++++------------
> include/linux/aer.h | 4 +-
> include/trace/events/ras.h | 77 ++++++++++++++++++++++++++++++++
> 4 files changed, 129 insertions(+), 34 deletions(-)
> create mode 100644 include/trace/events/ras.h
Pulled, thanks Tony!
Ingo
prev parent reply other threads:[~2013-01-24 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 21:08 [GIT PULL] Use perf/event tracing to report PCI Express advanced errors Luck, Tony
2013-01-24 13:49 ` Ingo Molnar [this message]
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=20130124134945.GB9715@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=lance.ortiz@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 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.