From: Nick Clifton <nickc@redhat.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [RESEND PATCH] gdb/or1k: Add linux debugging support
Date: Fri, 7 Dec 2018 15:18:26 +0000 [thread overview]
Message-ID: <52c4e267-4189-ed80-e045-e70f9d645df8@redhat.com> (raw)
In-Reply-To: <20181207063909.15365-1-shorne@gmail.com>
Hi Stafford,
> bfd/ChangeLog:
>
> * elf32-or1k.c (or1k_grok_prstatus): New function.
> (or1k_grok_psinfo): Likewise.
This part is approved.
Cheers
Nick
next prev parent reply other threads:[~2018-12-07 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 6:39 [OpenRISC] [RESEND PATCH] gdb/or1k: Add linux debugging support Stafford Horne
2018-12-07 15:18 ` Nick Clifton [this message]
2018-12-07 22:30 ` Stafford Horne
2018-12-11 12:40 ` Pedro Alves
2018-12-11 21:30 ` Stafford Horne
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=52c4e267-4189-ed80-e045-e70f9d645df8@redhat.com \
--to=nickc@redhat.com \
--cc=openrisc@lists.librecores.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.