From: Thomas Gleixner <tglx@linutronix.de>
To: mingo@redhat.com, hpa@zytor.com, paulus@samba.org,
acme@redhat.com, linux-kernel@vger.kernel.org,
fweisbec@gmail.com, a.p.zijlstra@chello.nl, namhyung@gmail.com,
ssp@redhat.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/cleanups] x86, dumpstack: Correct stack dump info when frame pointer is available
Date: Fri, 11 Mar 2011 20:54:16 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1103112052070.2787@localhost6.localdomain6> (raw)
In-Reply-To: <tip-074206a787e4dfdc4c290789ab6604c7f9e691ca@git.kernel.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 584 bytes --]
On Thu, 10 Mar 2011, tip-bot for Namhyung Kim wrote:
> Commit-ID: 074206a787e4dfdc4c290789ab6604c7f9e691ca
> Gitweb: http://git.kernel.org/tip/074206a787e4dfdc4c290789ab6604c7f9e691ca
> Author: Namhyung Kim <namhyung@gmail.com>
> AuthorDate: Tue, 8 Mar 2011 20:44:19 +0900
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Thu, 10 Mar 2011 23:20:30 +0100
>
> x86, dumpstack: Correct stack dump info when frame pointer is available
Dropped it due to:
arch/x86/oprofile/backtrace.c:130:8: error: too few arguments to function ‘dump_trace’
Thanks,
tglx
prev parent reply other threads:[~2011-03-11 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 11:44 [PATCH v4 -tip 1/4] " Namhyung Kim
2011-03-08 11:44 ` [PATCH v4 -tip 2/4] x86, dumpstack: Random printk changes Namhyung Kim
2011-03-10 22:25 ` [tip:x86/cleanups] x86, dumpstack: Cleanup printks tip-bot for Namhyung Kim
2011-03-08 11:44 ` [PATCH v4 -tip 3/4] x86, dumpstack: Rename print_context_stack and friends Namhyung Kim
2011-03-10 22:25 ` [tip:x86/cleanups] " tip-bot for Namhyung Kim
2011-03-08 11:44 ` [PATCH v4 -tip 4/4] x86, dumpstack: Use frame pointer during stack trace Namhyung Kim
2011-03-10 22:26 ` [tip:x86/cleanups] " tip-bot for Namhyung Kim
2011-03-10 23:02 ` Frederic Weisbecker
2011-03-23 13:08 ` Namhyung Kim
2011-03-23 14:08 ` Frederic Weisbecker
2011-03-23 14:36 ` Ingo Molnar
2011-03-10 22:24 ` [tip:x86/cleanups] x86, dumpstack: Correct stack dump info when frame pointer is available tip-bot for Namhyung Kim
2011-03-10 22:46 ` Frederic Weisbecker
2011-03-11 19:54 ` Thomas Gleixner [this message]
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=alpine.LFD.2.00.1103112052070.2787@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=ssp@redhat.com \
/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
all inboxes | Powered by JetHome®