public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: GDB patches <gdb-patches@sourceware.org>
Cc: Stafford Horne <shorne@gmail.com>
Subject: [PATCH 0/4] OpenRISC misc updates
Date: Thu, 14 Dec 2017 06:14:00 -0000	[thread overview]
Message-ID: <20171214061341.7797-1-shorne@gmail.com> (raw)

Hi All,

This is a series of a few misc patches for gdb and sim now that the or1k port
is upstream.  The paramater alignment updates are from some late whitespace
issues pointed out by Joel.

-Stafford

Stafford Horne (4):
  gdb: Add Stafford Horne as or1k maintainer.
  sim: Add Stafford Horne as or1k maintainer.
  gdb: Add news entries for new or1k target.
  gdb: Fix function parameter alignments in or1k-tdep.c.

 gdb/MAINTAINERS |  3 +++
 gdb/NEWS        |  4 ++++
 gdb/or1k-tdep.c | 18 +++++++++---------
 sim/MAINTAINERS |  1 +
 4 files changed, 17 insertions(+), 9 deletions(-)

-- 
2.13.6

             reply	other threads:[~2017-12-14  6:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  6:14 Stafford Horne [this message]
2017-12-14  6:14 ` [PATCH 4/4] gdb: Fix function parameter alignments in or1k-tdep.c Stafford Horne
2017-12-15 10:48   ` Yao Qi
2017-12-14  6:14 ` [PATCH 2/4] sim: Add Stafford Horne as or1k maintainer Stafford Horne
2017-12-26 13:53   ` Stafford Horne
2018-06-01 17:25     ` Simon Marchi
2018-06-03  3:29       ` Stafford Horne
2017-12-14  6:14 ` [PATCH 3/4] gdb: Add news entries for new or1k target Stafford Horne
2017-12-14 17:01   ` Eli Zaretskii
2017-12-14  6:14 ` [PATCH 1/4] gdb: Add Stafford Horne as or1k maintainer Stafford Horne
2017-12-26 13:53   ` Stafford Horne
2018-06-01 17:24     ` Simon Marchi
2018-06-03  3:26       ` 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=20171214061341.7797-1-shorne@gmail.com \
    --to=shorne@gmail.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).