From: "David S. Miller" <davem@redhat.com>
To: Hal Duston <hduston@speedscript.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible sparc64 signal handling issue
Date: Fri, 25 Jul 2003 13:39:24 -0700 [thread overview]
Message-ID: <20030725133924.13c7eff1.davem@redhat.com> (raw)
In-Reply-To: <1059164229.3926.16.camel@ulysseus>
Please report this to the sparc developer mailing list.
sparclinux@vger.kernel.org
Most Sparc developers do not read linux-kernel.
prev parent reply other threads:[~2003-07-25 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 20:17 Possible sparc64 signal handling issue Hal Duston
2003-07-25 20:39 ` David S. Miller [this message]
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=20030725133924.13c7eff1.davem@redhat.com \
--to=davem@redhat.com \
--cc=hduston@speedscript.com \
--cc=linux-kernel@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.