Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gbenson@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] Refactor shared code in {i386,amd64}-linux-nat.c
Date: Fri, 27 Jun 2014 09:28:00 -0000	[thread overview]
Message-ID: <201406270928.s5R9SZPG020219@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1403860209-475-1-git-send-email-gbenson@redhat.com> (message	from Gary Benson on Fri, 27 Jun 2014 10:10:02 +0100)

> From: Gary Benson <gbenson@redhat.com>
> Date: Fri, 27 Jun 2014 10:10:02 +0100
> 
> Hi all,
> 
> This series refactors the shared code in {i386,amd64}-linux-nat.c into
> the new files x86-linux-nat.[ch] and i386-linux-nat.h.  The first five
> patches remove spurious changes between the files so that the code to
> be shared is identical:
> 
>   1/7 - Rename identical functions
>   2/7 - Merge {i386,amd64}_linux_read_description
>   3/7 - Merge ps_get_thread_area
>   4/7 - Pull out common parts of _initialize_{i386,amd64}_linux_nat
>   5/7 - Comment and whitespace changes
> 
> The sixth patch moves the shared code into the new files and does all
> the makefile and build system updates:
> 
>   6/7 - Move duplicated code into new files
> 
> The seventh patch tidies the blocks of #include directives at the
> tops of {i386,amd64}-linux-nat.c:
> 
>   7/7 - Tidy #include lists
> 
> This final patch is not strictly necessary for the series, but it
> makes things tidier.
> 
> Is this ok to commit?

Sorry, no.  Perhaps more code can be shared between i386-linux-nat.c
and amd64-linux-nat.c, but this goes too far and turns things into
#ifdef spagetthi.  It also breaks established naming conventions.


  parent reply	other threads:[~2014-06-27  9:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27  9:10 Gary Benson
2014-06-27  9:10 ` [PATCH 3/7] Merge ps_get_thread_area Gary Benson
2014-06-27  9:10 ` [PATCH 6/7] Move duplicated code into new files Gary Benson
2014-06-27  9:10 ` [PATCH 2/7] Merge {i386,amd64}_linux_read_description Gary Benson
2014-06-27  9:10 ` [PATCH 4/7] Pull out common parts of _initialize_{i386,amd64}_linux_nat Gary Benson
2014-06-27  9:21   ` Mark Kettenis
2014-06-27  9:26 ` [PATCH 5/7] Comment and whitespace changes Gary Benson
2014-06-27  9:26 ` [PATCH 1/7] Rename identical functions Gary Benson
2014-06-27  9:28 ` Mark Kettenis [this message]
2014-06-27 10:39   ` [PATCH 0/7] Refactor shared code in {i386,amd64}-linux-nat.c Pedro Alves
2014-06-27 10:43     ` Pedro Alves
2014-06-27 10:54     ` Pedro Alves
2014-06-27 11:57   ` Gary Benson
2014-06-27  9:51 ` [PATCH 7/7] Tidy #include lists Gary Benson

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=201406270928.s5R9SZPG020219@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gbenson@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