public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Signal/gdb oddity in 2.5.61
Date: Sun, 16 Feb 2003 22:14:54 +0000	[thread overview]
Message-ID: <20030216221454.F12489@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030216221023.GA6806@nevyn.them.org>; from dan@debian.org on Sun, Feb 16, 2003 at 05:10:23PM -0500

On Sun, Feb 16, 2003 at 05:10:23PM -0500, Daniel Jacobowitz wrote:
> This is a consequence of ARM's separate get_signal_to_deliver. 
>
> Roland's changes for group stops require code in get_signal_to_deliver,
> so if you aren't using the common version, you're out of luck.
> 
> I think you'll have to either update yours to match, or use the new
> hooks David Miller added to use the common get_signal_to_deliver.

This is using the common version in 2.5.61.

You might want to completely review your reply in light of this.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-02-16 22:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-16 19:15 Signal/gdb oddity in 2.5.61 Russell King
2003-02-16 22:10 ` Daniel Jacobowitz
2003-02-16 22:14   ` Russell King [this message]
2003-02-16 22:21     ` Daniel Jacobowitz
2003-02-16 22:28       ` Russell King
     [not found] <Pine.LNX.4.44.0302161117370.2874-100000@home.transmeta.com>
2003-02-16 22:28 ` Roland McGrath
2003-02-16 23:27   ` Daniel Jacobowitz
2003-02-16 23:44     ` Linus Torvalds
2003-02-17  1:00     ` Roland McGrath
2003-02-17  2:34       ` Jeff Dike
2003-02-17  3:02       ` Daniel Jacobowitz

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=20030216221454.F12489@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox