From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH v5 2/3] aerdrv: Enhanced AER logging Date: Thu, 6 Dec 2012 11:24:37 +0100 Message-ID: <20121206102437.GB30885@liondog.tnic> References: <20121203212047.24373.8646.stgit@grignak.americas.hpqcorp.net> <20121203212053.24373.10914.stgit@grignak.americas.hpqcorp.net> <20121204093007.GG4369@liondog.tnic> <1354758031.17101.7.camel@gandalf.local.home> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <1354758031.17101.7.camel@gandalf.local.home> Sender: linux-pci-owner@vger.kernel.org To: Steven Rostedt Cc: Lance Ortiz , 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 List-Id: linux-acpi@vger.kernel.org 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.