From: "David S. Miller" <davem@redhat.com>
To: ac131313@cygnus.com
Cc: brobecker@ACT-Europe.FR, thorpej@wasabisystems.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix recent compilation errors in alpha-nat.c on alpha-osf
Date: Tue, 23 Apr 2002 22:04:00 -0000 [thread overview]
Message-ID: <20020423.215508.41659364.davem@redhat.com> (raw)
In-Reply-To: <3CC5EF51.2090803@cygnus.com>
From: Andrew Cagney <ac131313@cygnus.com>
Date: Tue, 23 Apr 2002 19:33:37 -0400
So it is certanly using the correct mechanism. Perhaphs if you can give
a concrete example it can be fixed.
Richard only told me in passing about this issue once, and
it sounded like he hadn't checked into this for some time.
I'll have him check the current code and whether the problem
still exists, and if so field more information.
prev parent reply other threads:[~2002-04-24 5:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 6:42 Joel Brobecker
2002-04-22 8:49 ` Jason R Thorpe
2002-04-22 8:56 ` Jason R Thorpe
2002-04-23 3:14 ` Joel Brobecker
2002-04-23 3:55 ` David S. Miller
2002-04-23 10:56 ` Michael Snyder
2002-04-23 16:33 ` Andrew Cagney
2002-04-23 22:04 ` 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=20020423.215508.41659364.davem@redhat.com \
--to=davem@redhat.com \
--cc=ac131313@cygnus.com \
--cc=brobecker@ACT-Europe.FR \
--cc=gdb-patches@sources.redhat.com \
--cc=thorpej@wasabisystems.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