From: Borislav Petkov <bp@alien8.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Lance Ortiz <lance.ortiz@hp.com>,
bhelgaas@google.com, lance_ortiz@hotmail.com,
jiang.liu@huawei.com, tony.luck@intel.com, mchehab@redhat.com,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] aerdrv: Enhanced AER logging
Date: Thu, 6 Dec 2012 11:24:37 +0100 [thread overview]
Message-ID: <20121206102437.GB30885@liondog.tnic> (raw)
In-Reply-To: <1354758031.17101.7.camel@gandalf.local.home>
On Wed, Dec 05, 2012 at 08:40:31PM -0500, Steven Rostedt wrote:
> You can have a config that enables these trace points, and when you
> enable one of the systems that uses them, have that config select the
> config that enables tracepoints. Have that config compile the file for
> tracepoints. For example, in a Makefile:
>
> obj-$(CONFIG_RAS_TRACE_POINTS) += ras-trace.o
>
>
> Use #ifdef CONFIG_FOO_BAR around tracepoints that are required for
> specific systems if the tracepoints in the header file are for different
> subsystems that can be enabled or disabled separately by configs.
Cool, this sounds exactly like what we should do, I'll hack it up soon.
Thanks a lot.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-12-06 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 21:20 [PATCH v5 1/3] aerdrv: Trace Event for AER Lance Ortiz
2012-12-03 21:20 ` [PATCH v5 2/3] aerdrv: Enhanced AER logging Lance Ortiz
2012-12-04 9:30 ` Borislav Petkov
2012-12-06 1:40 ` Steven Rostedt
2012-12-06 10:24 ` Borislav Petkov [this message]
2012-12-03 21:21 ` [PATCH v5 3/3] aerdrv: Cleanup log output for CPER based AER Lance Ortiz
2012-12-04 9:22 ` [PATCH v5 1/3] aerdrv: Trace Event for AER Borislav Petkov
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=20121206102437.GB30885@liondog.tnic \
--to=bp@alien8.de \
--cc=bhelgaas@google.com \
--cc=jiang.liu@huawei.com \
--cc=lance.ortiz@hp.com \
--cc=lance_ortiz@hotmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mchehab@redhat.com \
--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