From: Andi Kleen <andi@firstfloor.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: Andi Kleen <andi@firstfloor.org>,
akpm@linux-foundation.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [3/3] Fix unwind annotations for 64bit kernel
Date: Mon, 7 Dec 2009 10:06:34 +0100 [thread overview]
Message-ID: <20091207090634.GC18989@one.firstfloor.org> (raw)
In-Reply-To: <4B1CC28F0200007800024075@vpn.id2.novell.com>
> So do we, but the initial submission was rejected due to doing too many
> things at once. I didn't since find time (admittedly also because not
> giving it priority) to split the patch. Thanks for giving it another try!
I'm not sure what should be split, it's all related and straight forward.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-12-07 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 14:13 [PATCH] [1/3] x86: Improve CONFIG_KEXEC_JUMP description Andi Kleen
2009-12-06 14:13 ` [PATCH] [2/3] x86: Remove CONFIG_GBPAGES option Andi Kleen
2009-12-06 14:13 ` [PATCH] [3/3] Fix unwind annotations for 64bit kernel Andi Kleen
2009-12-07 7:53 ` Jan Beulich
2009-12-07 9:06 ` Andi Kleen [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=20091207090634.GC18989@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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