mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexander van Heukelum <heukelum@fastmail.fm>,
	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:07:36 -0400	[thread overview]
Message-ID: <20081027200736.GA3220@hmsreliant.think-freely.org> (raw)
In-Reply-To: <20081027182148.GL3046@elte.hu>

On Mon, Oct 27, 2008 at 07:21:48PM +0100, Ingo Molnar wrote:
> 
> * Alexander van Heukelum <heukelum@fastmail.fm> wrote:
> 
> > On Thu, 23 Oct 2008 10:40:06 -0400, "Neil Horman"
> > <nhorman@tuxdriver.com> said:
> > > 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>
> > 
> > A bit late, maybe, but if it matters:
> > 
> > Acked-by: Alexander van Heukelum <heukelum@fastmail.fm>
> 
> i've updated the commit, thanks.
> 
> 	Ingo
> 

Thanks guys!
Neil

-- 
/****************************************************
 * Neil Horman <nhorman@tuxdriver.com>
 * Software Engineer, Red Hat
 ****************************************************/

      reply	other threads:[~2008-10-27 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 14:40 Neil Horman
2008-10-27 15:20 ` Ingo Molnar
2008-10-27 17:27 ` Alexander van Heukelum
2008-10-27 18:21   ` Ingo Molnar
2008-10-27 20:07     ` Neil Horman [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=20081027200736.GA3220@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=heukelum@fastmail.fm \
    --cc=heukelum@mailshack.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.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 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®