Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:53617 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753666Ab2CZItc (ORCPT ); Mon, 26 Mar 2012 04:49:32 -0400 Message-ID: <1332751768.3511.3.camel@jlt3.sipsolutions.net> (sfid-20120326_104947_617198_D5CF29BA) Subject: Re: [PATCH 4/4] compat: add some tracing backport work From: Johannes Berg To: "Luis R. Rodriguez" Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, lf_driver_backport@lists.linux-foundation.org Date: Mon, 26 Mar 2012 10:49:28 +0200 In-Reply-To: (sfid-20120322_053002_038310_D468A77C) References: <1332214021-9716-1-git-send-email-mcgrof@frijolero.org> <1332214021-9716-5-git-send-email-mcgrof@frijolero.org> <1332245766.3329.14.camel@jlt3.sipsolutions.net> (sfid-20120322_053002_038310_D468A77C) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, 2012-03-21 at 21:29 -0700, Luis R. Rodriguez wrote: > But no dice. I then figured it may be my kernel with > CONFIG_TRACEPOINTS=y and indeed that is the case -- so we have to > consider the case where the target kernel may have tracing enabled and > we have to disable it somehow. Undef'ing CONFIG_TRACEPOINTS and > DECLARE_TRACE doesn't really do it. Oh, ok, yuck. So I guess we can't easily disable tracing if it's enabled in the base kernel ... > We may need to redefine each macro to some COMPAT_TRACE_ macro, not sure yet. That would require patches again though, no fun either. johannes