From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [patch] ftrace, v15
Date: Sat, 26 Apr 2008 23:32:40 -0700 (PDT) [thread overview]
Message-ID: <20080426.233240.252075490.davem@davemloft.net> (raw)
In-Reply-To: <20080427063019.GA23295@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Sun, 27 Apr 2008 08:30:19 +0200
> sched: fix rq->clock overflows detection with CONFIG_NO_HZ
> sched: make sure jiffies is up to date before calling __update_rq_clock()
You're getting sloppier and sloppier each and every bogus pull request
you send out this week Ingo.
What is all of this non-ftrace crap in the shortlog?
next prev parent reply other threads:[~2008-04-27 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 6:30 [patch] ftrace, v15 Ingo Molnar
2008-04-27 6:32 ` David Miller [this message]
2008-04-27 7:16 ` Ingo Molnar
2008-04-27 7:22 ` David Miller
2008-04-27 11:14 ` KOSAKI Motohiro
2008-04-27 13:15 ` 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=20080426.233240.252075490.davem@davemloft.net \
--to=davem@davemloft.net \
--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