From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.4.21-ia64-030702 arch/ia64/kernel/unwind.c
Date: Tue, 29 Jul 2003 23:26:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105952134021957@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105909779318784@msgid-missing>
On Thursday 24 July 2003 2:59 am, Keith Owens wrote:
> On Sun, 20 Jul 2003 19:51:06 +1000,
> Keith Owens <kaos@sgi.com> wrote:
> >This has been fixed once but must have slipped through the cracks. It
> >only shows up when you turn on unwind debugging.
>
> And another one, again it only shows up with unwind debugging.
>
> --- linux/arch/ia64/kernel/unwind.c 2003-07-03 12:03:40.000000000 +1000
> +++ linux/arch/ia64/kernel/unwind.c 2003-07-24 16:45:34.000000000 +1000
> @@ -1955,7 +1955,7 @@
> " bsp 0x%lx\n"
> " sof 0x%lx\n"
> " ip 0x%lx\n",
> - info->bsp, sof, info->ip);
> + __FUNCTION__, info->bsp, sof, info->ip);
> find_save_locs(info);
> }
>
> @@ -1973,7 +1973,7 @@
> " bsp 0x%lx\n"
> " sol 0x%lx\n"
> " ip 0x%lx\n",
> - info->bsp, sol, info->ip);
> + __FUNCTION__, info->bsp, sol, info->ip);
> find_save_locs(info);
> }
I applied this one, too. And I'll push the changes to bkbits and kernel.org
in a minute.
Bjorn
next prev parent reply other threads:[~2003-07-29 23:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 8:59 [patch] 2.4.21-ia64-030702 arch/ia64/kernel/unwind.c Keith Owens
2003-07-29 23:21 ` Bjorn Helgaas
2003-07-29 23:26 ` Bjorn Helgaas [this message]
2003-08-07 23:03 ` [patch] 2.4.21-ia64-030702 arch/ia64/kernel/mca.c Bjorn Helgaas
2003-08-08 0:41 ` Keith Owens
2003-08-08 16:12 ` Bjorn Helgaas
2003-08-08 17:15 ` Bjorn Helgaas
2003-08-10 5:08 ` Keith Owens
2003-08-10 5:28 ` Alex Williamson
2003-08-11 23:01 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2003-07-20 9:51 [patch] 2.4.21-ia64-030702 arch/ia64/kernel/unwind.c Keith Owens
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-105952134021957@msgid-missing \
--to=bjorn.helgaas@hp.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 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.