All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: Question about signal syscalls !
Date: Thu, 1 Feb 2007 18:10:28 +0000	[thread overview]
Message-ID: <20070201181028.GA16964@linux-mips.org> (raw)
In-Reply-To: <cda58cb80702010654w74527a34k4ed229b499b8f9b2@mail.gmail.com>

On Thu, Feb 01, 2007 at 03:54:40PM +0100, Franck Bui-Huu wrote:

> Let's take for example sys_sigreturn(). In my understanding this
> syscall is used automatically when the signal handler returns. At this
> time, I don't see the point to save the static registers since they
> have been already saved by setup_sigcontext().
> 
> Actually I don't see why they need to be saved/restored at all...

There is no need.  Seems you found a harmless but longstanding but
introduced by c40738a70f3e02e8554b78af334dc95356a78989.

  Ralf

  parent reply	other threads:[~2007-02-01 18:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 10:43 Question about signal syscalls ! Franck Bui-Huu
2007-02-01 13:57 ` Ralf Baechle
2007-02-01 14:54   ` Franck Bui-Huu
2007-02-01 17:01     ` David Daney
2007-02-02  8:55       ` Franck Bui-Huu
2007-02-02 16:04         ` David Daney
2007-02-02 16:36           ` Franck Bui-Huu
2007-02-02 16:53             ` Daniel Jacobowitz
2007-02-02 20:03               ` Franck Bui-Huu
2007-02-02 20:18               ` Franck Bui-Huu
2007-02-02 16:56             ` David Daney
2007-02-02 19:58               ` Franck Bui-Huu
2007-02-02 20:41                 ` David Daney
2007-02-05  0:55                   ` Daniel Jacobowitz
2007-02-05  1:10                     ` Ralf Baechle
2007-02-05  2:30                       ` Daniel Jacobowitz
2007-02-05  6:00                         ` David Daney
2007-02-05  9:17                         ` Franck Bui-Huu
2007-02-05  9:08                       ` Franck Bui-Huu
2007-02-01 18:10     ` Ralf Baechle [this message]
2007-02-02  8:54       ` Franck Bui-Huu

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=20070201181028.GA16964@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=vagabon.xyz@gmail.com \
    /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.