From: Ingo Molnar <mingo@elte.hu>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org,
Alexander van Heukelum <heukelum@mailshack.com>,
Thomas Gleixner <tglx@linutronix.de>,
mingo@redhat.com, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86: unify appropriate bits from dumpstack_32 and dumpstack_64
Date: Mon, 27 Oct 2008 16:20:22 +0100 [thread overview]
Message-ID: <20081027152021.GF5704@elte.hu> (raw)
In-Reply-To: <20081023144006.GA14149@hmsendeavour.rdu.redhat.com>
* Neil Horman <nhorman@tuxdriver.com> wrote:
> Hey all-
> As promised, now that dumpstack_32 and dumpstack_64 have so
> many bits in common, we should merge the in-sync bits into a common
> file, to prevent them from diverging again. This patch removes bits
> which are common between dumpstack_32.c and dumpstack_64.c and
> places them in a common dumpstack.c which is built for both 32 and
> 64 bit arches.
>
> Regards
> Neil
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
>
>
> Makefile | 2
> dumpstack.c | 319 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> dumpstack.h | 39 ++++++
> dumpstack_32.c | 294 ----------------------------------------------------
> dumpstack_64.c | 285 --------------------------------------------------
> 5 files changed, 363 insertions(+), 576 deletions(-)
applied to tip/x86/dumpstack, thanks Neil!
Ingo
next prev parent reply other threads:[~2008-10-27 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 14:40 [PATCH] x86: unify appropriate bits from dumpstack_32 and dumpstack_64 Neil Horman
2008-10-27 15:20 ` Ingo Molnar [this message]
2008-10-27 17:27 ` Alexander van Heukelum
2008-10-27 18:21 ` Ingo Molnar
2008-10-27 20:07 ` Neil Horman
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=20081027152021.GF5704@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=heukelum@mailshack.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=tglx@linutronix.de \
/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.