From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@lst.de>,
Steven Rostedt <rostedt@goodmis.org>,
"Fr?d?ric Weisbecker" <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kill markers
Date: Fri, 18 Sep 2009 08:41:09 -0400 [thread overview]
Message-ID: <20090918124109.GE1173@Krystal> (raw)
In-Reply-To: <20090918123846.GB24391@elte.hu>
* Ingo Molnar (mingo@elte.hu) wrote:
>
> * Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
>
> > * Ingo Molnar (mingo@elte.hu) wrote:
> > >
> > > * Christoph Hellwig <hch@lst.de> wrote:
> > >
> > > > Now that the last users of markers have migrated to the event tracer
> > > > we can kill off the support code.
> > >
> > > Applied, thanks Christoph!
> > >
> > > Btw., there's some more marker related bits in the kernel, such as
> > > scripts/mod/modpost.c - mostly the effects of:
> > >
> > > b2e3e65: Linux Kernel Markers: create modpost file
> > >
> > > I think we want to keep those bits, for those who want to use new
> > > modpost with an older kernel - but mark them for deprecation.
> >
> > Just to confirm: this means having a printk-style infrastructure to
> > prototype tracepoints is not considered useful ?
>
> trace_printk()?
OK, sounds good !
No objection then :)
Thanks,
Mathieu
>
> Ingo
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-09-18 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 17:35 [PATCH] kill markers Christoph Hellwig
2009-09-18 10:23 ` Ingo Molnar
2009-09-18 12:13 ` Mathieu Desnoyers
2009-09-18 12:38 ` Ingo Molnar
2009-09-18 12:41 ` Mathieu Desnoyers [this message]
2009-09-18 12:45 ` Ingo Molnar
2009-09-18 10:48 ` [tip:tracing/urgent] tracing: Remove markers tip-bot for Christoph Hellwig
2009-09-18 12:48 ` tip-bot for Christoph Hellwig
2009-09-18 19:24 ` tip-bot for Christoph Hellwig
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=20090918124109.GE1173@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=fweisbec@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 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.