From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
lf_driver_backport@lists.linux-foundation.org
Subject: Re: [PATCH 4/4] compat: add some tracing backport work
Date: Mon, 26 Mar 2012 10:49:28 +0200 [thread overview]
Message-ID: <1332751768.3511.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6XXd-T5B37Cc_eCwnWHRk-_UVn0JY0mQjzMQcK+ZcLuWQ@mail.gmail.com> (sfid-20120322_053002_038310_D468A77C)
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
next prev parent reply other threads:[~2012-03-26 8:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 3:26 [PATCH 0/4] compat: March 19 backport work Luis R. Rodriguez
2012-03-20 3:26 ` [PATCH 1/4] compat: backport system work queues system_wq and system_long_wq Luis R. Rodriguez
2012-03-20 3:26 ` [PATCH 2/4] compat: backport work_busy() Luis R. Rodriguez
2012-03-20 12:07 ` Johannes Berg
2012-03-20 13:50 ` Luis R. Rodriguez
2012-03-20 14:29 ` [Lf_driver_backport] " Anderson Lizardo
2012-03-20 14:30 ` Anderson Lizardo
2012-03-20 3:27 ` [PATCH 3/4] compat: fix load time issue with kfifo backport Luis R. Rodriguez
2012-03-20 3:27 ` [PATCH 4/4] compat: add some tracing backport work Luis R. Rodriguez
2012-03-20 12:11 ` Johannes Berg
2012-03-20 12:16 ` Johannes Berg
2012-03-20 13:53 ` Luis R. Rodriguez
2012-03-22 4:29 ` Luis R. Rodriguez
2012-03-26 8:49 ` Johannes Berg [this message]
2012-03-26 12:58 ` Luis R. Rodriguez
2012-03-28 10:00 ` Luis R. Rodriguez
2012-04-05 12:33 ` Johannes Berg
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=1332751768.3511.3.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=lf_driver_backport@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
/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