From: Philipp Rudo <prudo@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>,
Ulrich Weigand <uweigand@de.ibm.com>
Subject: [PATCH 0/4] Split up s390-linux-tdep.c
Date: Thu, 23 Nov 2017 15:37:00 -0000 [thread overview]
Message-ID: <20171123153733.31261-1-prudo@linux.vnet.ibm.com> (raw)
Hi everybody
This patch set splits up the s390 tdep code followed by some minor clean up
and coding style fixes. It originates from my Linux kernel feature and
helps adding the new Linux kernel 'OS' to s390 while keeping the code
manageable. I want to bring the set upstream in advance of the rest of the
kernel debugging feature as nearly all changes to s390-linux-tdep.c cause
merge conflicts making the maintenance off-tree extremely labor intensive
and error prone.
Thanks
Philipp
Philipp Rudo (4):
Split up s390-linux-tdep.c into two files
Clean up s390-linux-tdep.c
Add comments to uncommented functions in s390-tdep.c
Add comments to uncommented functions in s390-linux-tdep.c
gdb/Makefile.in | 3 +
gdb/configure.tgt | 4 +-
gdb/s390-linux-nat.c | 1 +
gdb/s390-linux-tdep.c | 2933 +++----------------------------------------------
gdb/s390-linux-tdep.h | 194 +---
gdb/s390-tdep.c | 2658 ++++++++++++++++++++++++++++++++++++++++++++
gdb/s390-tdep.h | 386 +++++++
7 files changed, 3202 insertions(+), 2977 deletions(-)
create mode 100644 gdb/s390-tdep.c
create mode 100644 gdb/s390-tdep.h
--
2.13.5
next reply other threads:[~2017-11-23 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 15:37 Philipp Rudo [this message]
2017-11-23 15:37 ` [PATCH 4/4] Add comments to uncommented functions in s390-linux-tdep.c Philipp Rudo
2017-11-23 15:37 ` [PATCH 3/4] Add comments to uncommented functions in s390-tdep.c Philipp Rudo
2017-11-23 15:38 ` [PATCH 2/4] Clean up s390-linux-tdep.c Philipp Rudo
2017-11-23 15:38 ` [PATCH 1/4] Split up s390-linux-tdep.c into two files Philipp Rudo
2017-11-23 20:26 ` Ulrich Weigand
2017-11-24 16:55 ` Philipp Rudo
2017-11-24 19:25 ` Ulrich Weigand
2017-11-28 9:34 ` Philipp Rudo
2017-11-28 19:31 ` Ulrich Weigand
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=20171123153733.31261-1-prudo@linux.vnet.ibm.com \
--to=prudo@linux.vnet.ibm.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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