From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] More procfs.c simplification
Date: Wed, 02 May 2018 23:58:00 -0000 [thread overview]
Message-ID: <faaa330d-44db-96e4-0c42-44def126e99b@redhat.com> (raw)
In-Reply-To: <20180412165934.27722-1-palves@redhat.com>
On 04/12/2018 05:59 PM, Pedro Alves wrote:
> There are only two architectures using procfs.c (i386/SPARC), and none
> of their corresponding nat files overrides any target method. Move
> the add_target calls to procfs.c directly.
>
> gdb/ChangeLog:
> yyyy-mm-dd Pedro Alves <palves@redhat.com>
>
> * i386-sol2-nat.c (_initialize_amd64_sol2_nat): Don't call
> procfs_target/add_target here.
> * procfs.c (procfs_target): Make static.
> (_initialize_procfs): Call add_target here.
> * procfs.h (struct target_ops): Remove forward declaration.
> (procfs_target): Remove declaration.
> * sparc-sol2-nat.c (_initialize_sparc_sol2_nat): Delete.
I pushed this one in too.
Thanks,
Pedro Alves
prev parent reply other threads:[~2018-05-02 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 16:59 Pedro Alves
2018-05-02 23:58 ` Pedro Alves [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=faaa330d-44db-96e4-0c42-44def126e99b@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).