Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: James Bowman <james.bowman@ftdichip.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, FT32] Proper support for address <-> pointer conversions
Date: Tue, 22 Sep 2015 19:54:00 -0000	[thread overview]
Message-ID: <CADPb22SwEhFcgaKyJJqnFm_T1XuhB8xuLzwC-VjncnNbgfmkFA@mail.gmail.com> (raw)
In-Reply-To: <CA9BBF0458F83C4F9051448B941B57D119614FCF@glaexch1>

On Tue, Sep 22, 2015 at 11:37 AM, James Bowman
<james.bowman@ftdichip.com> wrote:
> Thanks for the review. Corrected Changelog/patch is below.
>
> However I was not sure about splitting -- these changes all
> seem to go together. That is, applying just some of the patch
> results in a non-functioning gdb.
>
> 2015-09-22  James Bowman  <james.bowman@ftdichip.com>
>
>         * ft32-tdep.c: Implement the pointer to address method so
>         that FT32's address spaces (RAM and flash) work correctly when
>         dereferencing pointers in gdb. Also make PC a flash pointer.
>         * ft32-tdep.h: Add a type for an address space 1 pointer, for
>         the PC.

Yeah, there'll always be some grey area as to when one should split up a patch.
This patch is small enough and is completely target specific.

The ChangeLog is still incorrect though. E.g. compare with just about
every existing changelog entry.
gdb's pretty good at following its own conventions, and that in turn
makes it easy to continue to follow them.
Just go with the flow and mimic (without being creative) what's already there.
There's also:
https://sourceware.org/gdb/wiki/ContributionChecklist


  reply	other threads:[~2015-09-22 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 23:07 James Bowman
2015-09-22 16:36 ` Yao Qi
2015-09-22 18:38   ` James Bowman
2015-09-22 19:54     ` Doug Evans [this message]
2015-09-22 22:10       ` James Bowman
2015-09-23  7:46         ` Yao Qi

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=CADPb22SwEhFcgaKyJJqnFm_T1XuhB8xuLzwC-VjncnNbgfmkFA@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=james.bowman@ftdichip.com \
    --cc=qiyaoltc@gmail.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