From: Paul Mundt <lethal@linux-sh.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@lst.de>,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
Fr?d?ric Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] sh: remove stray markers
Date: Thu, 7 May 2009 11:04:36 +0900 [thread overview]
Message-ID: <20090507020436.GB7938@linux-sh.org> (raw)
In-Reply-To: <20090506111549.GJ25203@elte.hu>
On Wed, May 06, 2009 at 01:15:49PM +0200, Ingo Molnar wrote:
>
> * Christoph Hellwig <hch@lst.de> wrote:
>
> > On Wed, May 06, 2009 at 01:07:35PM +0200, Ingo Molnar wrote:
> > > Also, if there's some current use of these markers then it's OK
> > > to not do this change right now but replace them with
> > > tracepoints in the v2.6.31 merge window, after both the SH and
> > > the tracing infrastructure changes are upstream.
> >
> > There's not user of these. [...]
>
> I'll defer to Paul to decide whether SH needs those markers. If he
> added them to ease his own debugging (via whatever external
> approach), then that's an OK goal and we can handle this all
> politely without destroying functionality, in the next merge window.
>
They were primarily added to aid some downstream folks that were just
adding these on their own and generally not paying attention to where the
markers were being placed on subsequent merges. I don't feel too strongly
one way or the other, but as they have proven to be useful for some
people, I would rather transition over to tracepoints during the merge
window than kill them off prematurely.
next prev parent reply other threads:[~2009-05-07 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 10:38 [PATCH] sh: remove stray markers Christoph Hellwig
2009-05-06 11:07 ` Ingo Molnar
2009-05-06 11:12 ` Christoph Hellwig
2009-05-06 11:15 ` Ingo Molnar
2009-05-07 2:04 ` Paul Mundt [this message]
2009-05-07 7:30 ` Ingo Molnar
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=20090507020436.GB7938@linux-sh.org \
--to=lethal@linux-sh.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox