From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [patch] 2.4.20 unwind.c to handle multiple struct pt_regs
Date: Sun, 02 Mar 2003 05:15:47 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805953@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805882@msgid-missing>
On Thu, 20 Feb 2003 12:29:20 +1100,
Keith Owens <kaos@sgi.com> wrote:
>>The patch basically looks fine to me, except that I'd really like to
>>prefer to have it split up into one patch that does the pt_regs fixes
>>and one that does the debug enhancements. And while you're at it,
>>please use something a bit more concise than UNW_DEBUG_PRINT
>>(something like DPRINT or UNW_DPRINT should be sufficient).
>
>Two patches follow. The first updates include/asm-ia64/unwind.h,
>arch/ia64/kernel/unwind_i.h, arch/ia64/kernel/unwind.c to handle
>multiple pt_regs on stack. The second only updates unwind.c, it goes
>over the first patch to clean up the debug code, using UNW_DPRINT().
This patch was not included in the ia64 bundle for 2.4.21-pre5. Are
there any problems with the patch? Do I need to send it again? It
applies over 2.4.21-pre5 with a 2 line offset on the last hunk.
next prev parent reply other threads:[~2003-03-02 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 1:29 [Linux-ia64] Re: [patch] 2.4.20 unwind.c to handle multiple struct pt_regs Keith Owens
2003-03-02 5:15 ` Keith Owens [this message]
2003-03-03 16:47 ` Bjorn Helgaas
2003-03-03 23:52 ` Keith Owens
2003-03-04 22:06 ` David Mosberger
2003-03-07 19:22 ` Bjorn Helgaas
2003-03-11 16:23 ` Bjorn Helgaas
2003-03-12 1:54 ` Keith Owens
2003-03-12 2:58 ` Matthew Wilcox
2003-03-12 7:22 ` [Linux-ia64] Re: [patch] 2.4.20 unwind.c to handle multiple David Woodhouse
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=marc-linux-ia64-105590709805953@msgid-missing \
--to=kaos@sgi.com \
--cc=linux-ia64@vger.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