From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stef Simoens <stef.simoens@pi.be>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] PPC601 MQ handling
Date: Thu, 17 Jun 2004 11:27:06 -0500 [thread overview]
Message-ID: <1087489624.8556.248.camel@gaston> (raw)
In-Reply-To: <HZG4L6$A14A0723F533A1C86A3AF192DB6EF298@scarlet.be>
On Thu, 2004-06-17 at 04:19, Stef Simoens wrote:
> > Did you check it was actually saved/restored by the signal code ?
> >
> > Ben.
>
> I looked up when XER gets saved/restored to save/restore MQ.
>
> I tested my patch with
> mqtest &
> (start other programs which are 'MQ-enabled')
> fg
> ^Z
> ...
> and mqtest gave me the correct output.
I was concerned about arch/ppc/kernel/signal.c but it seems that it's ok,
it will save & restore it properly.
Paul, do we want this patch in ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-17 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 9:19 [PATCH] PPC601 MQ handling Stef Simoens
2004-06-17 16:27 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-16 20:42 Stef Simoens
2004-06-16 20:44 ` Benjamin Herrenschmidt
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=1087489624.8556.248.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=stef.simoens@pi.be \
/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).