public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Openrisc <openrisc@lists.librecores.org>
Cc: Yao Qi <qiyaoltc@gmail.com>, Doug Evans <dje@google.com>,
	Simon Marchi <simon.marchi@polymtl.ca>,
	GDB patches <gdb-patches@sourceware.org>
Subject: or1k GDB port - upstream now
Date: Tue, 12 Dec 2017 15:10:00 -0000	[thread overview]
Message-ID: <20171212151030.GC3483@lianli.shorne-pla.net> (raw)

Hi All,

I have just pushed the or1k port of gdb upstream.  Thanks to all those that have
helped review patches over the last year.

There are still a few things left to do:

Tomorrow or Next day
 - MAINTAINERS - add myself for or1k port
 - NEWS - add a news line for the or1k port

Next few weeks
 - arbitrary reggroups - finish up my tdesc patch [0]

Long term
 - linux support - add linux debugging support

Please let me know if there are any concerns or anything I am missing.

-Stafford

[0] https://sourceware.org/ml/gdb-patches/2017-06/msg00187.html

                 reply	other threads:[~2017-12-12 15:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171212151030.GC3483@lianli.shorne-pla.net \
    --to=shorne@gmail.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=openrisc@lists.librecores.org \
    --cc=qiyaoltc@gmail.com \
    --cc=simon.marchi@polymtl.ca \
    /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).