Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Michael Snyder <msnyder@redhat.com>,
	gdb@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Time for a shared linux-nat.c module?
Date: Tue, 23 Apr 2002 14:29:00 -0000	[thread overview]
Message-ID: <1020423212807.ZM10428@localhost.localdomain> (raw)
In-Reply-To: Michael Snyder <msnyder@redhat.com> "[RFC] Time for a shared linux-nat.c module?" (Apr 23,  1:21pm)

On Apr 23,  1:21pm, Michael Snyder wrote:

> I notice that there are now a bunch of <arch>-linux-tdep.c 
> modules, and that some of them share a bunch of duplicate code.  
> 
> I'm wondering if it isn't time to create a linux-nat.c module, 
> shared by all host architectures, into which we can move
> some of this code instead of maintaining separate, duplicate
> versions.

You meant a shared linux-tdep.c, right?  (Not -nat.c)  Assuming that this is
the case, I think your idea makes sense.

Kevin


  reply	other threads:[~2002-04-23 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 13:33 Michael Snyder
2002-04-23 14:29 ` Kevin Buettner [this message]
2002-04-23 22:03 ` David S. Miller
2002-04-24  8:27   ` [RFA] Add glibc-tdep (was Re: [RFC] Time for a shared linux-nat.c module?) David S. Miller

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=1020423212807.ZM10428@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=msnyder@redhat.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