From: Ingo Molnar <mingo@elte.hu>
To: Alexander van Heukelum <heukelum@fastmail.fm>
Cc: LKML <linux-kernel@vger.kernel.org>,
Vegard Nossum <vegard.nossum@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] x86: split out dumpstack code from traps_xx.c
Date: Tue, 30 Sep 2008 13:44:37 +0200 [thread overview]
Message-ID: <20080930114437.GF21367@elte.hu> (raw)
In-Reply-To: <1222773135-1073-1-git-send-email-heukelum@fastmail.fm>
* Alexander van Heukelum <heukelum@fastmail.fm> wrote:
> Patches are against the current master branch of the tip tree. The
> defconfigs compile fine and I ran some simple configs within qemu.
applied to tip/x86/traps:
# 9bb2b4f: x86_64: split out dumpstack code from traps_64.c
# f616942: i386: split out dumpstack code from traps_32.c
there were some interactions with other branches:
054efa5: Merge branch 'tracing/nmisafe' into x86/traps
9ecb7cf: Merge branch 'kmemcheck' into x86/traps
8955b63: Merge branch 'core/signal' into x86/traps
ff1b7a8: Merge branch 'x86/signal' into x86/traps
76b22d8: Merge commit 'v2.6.27-rc8' into x86/traps
b58c936: Merge branch 'x86/core' into x86/traps
I hope i sorted them out right.
Ingo
prev parent reply other threads:[~2008-09-30 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 11:12 [PATCH 0/2] x86: split out dumpstack code from traps_xx.c Alexander van Heukelum
2008-09-30 11:12 ` [PATCH 1/2] i386: split out dumpstack code from traps_32.c Alexander van Heukelum
2008-09-30 11:12 ` [PATCH 2/2] x86_64: split out dumpstack code from traps_64.c Alexander van Heukelum
2008-09-30 11:27 ` [PATCH 0/2] x86: split out dumpstack code from traps_xx.c Ingo Molnar
2008-09-30 11:44 ` Ingo Molnar [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=20080930114437.GF21367@elte.hu \
--to=mingo@elte.hu \
--cc=heukelum@fastmail.fm \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.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 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.