From: Olaf Hering <olh@suse.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Michael Ellerman <michael@ellerman.id.au>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] return to OF via trap, not exit
Date: Mon, 6 Mar 2006 08:43:39 +0100 [thread overview]
Message-ID: <20060306074339.GC24869@suse.de> (raw)
In-Reply-To: <590CA2B3-AACE-4B69-930D-9A66A42FFC83@kernel.crashing.org>
On Mon, Mar 06, Segher Boessenkool wrote:
> >Which is likely ok because it saves us from typing .registers
> >manually.
>
> I can't say that's a great argument. How about doing the trap thing
> on "known-bad" platforms only?
Can you do anything at that time anyway? I mean, reset-all pending
either way.
next prev parent reply other threads:[~2006-03-06 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 19:10 [PATCH] return to OF via trap, not exit Olaf Hering
2006-03-06 1:12 ` Michael Ellerman
2006-03-06 7:38 ` Olaf Hering
2006-03-06 7:41 ` Segher Boessenkool
2006-03-06 7:43 ` Olaf Hering [this message]
2006-03-06 7:46 ` Segher Boessenkool
2006-03-06 7:49 ` Olaf Hering
2006-03-06 7:57 ` Segher Boessenkool
2006-03-23 21:03 ` Olaf Hering
2006-03-23 23:11 ` Michael Ellerman
2006-03-24 12:13 ` Segher Boessenkool
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=20060306074339.GC24869@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).