From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Langlois <pierre.langlois@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Backport AVR fixes
Date: Thu, 10 Apr 2014 17:41:00 -0000 [thread overview]
Message-ID: <20140410174101.GA27126@adacore.com> (raw)
In-Reply-To: <20140410173837.GL4250@adacore.com>
> > Would it be OK to backport these two commits to gdb-7.7-branch for the next
> > 7.7.1 release?
> >
> > https://sourceware.org/ml/gdb-patches/2014-04/msg00097.html
> > https://sourceware.org/ml/gdb-patches/2014-03/msg00425.html
> >
> > I am not yet familiar with the process of backporting patches in GDB, let me
> > know if I am doing this correctly. For instance, should I break this into
> > several commits?
> >
> > Best,
> >
> > Pierre
> >
> > 2014-04-08 Pierre Langlois <pierre.langlois@embecosm.com>
> >
> > * avr-tdep.c (struct gdbarch_tdep): Mention avrxmega in the comment.
> > (avr_gdbarch_init): Add xmega architectures given by bfd_architecture
> > when setting the size of call_length.
> > (avr_scan_prologue): Accept push r1 instruction for small stack
> > allocation.
> > * MAINTAINERS (Write After Approval): Add "Pierre Langlois".
>
> Sure, go ahead. Please remember to confirm with a quick email on this
> list when the push is done. This helps archeologist reviewing the emails
> sent on this list.
I FORGOT! Please also update "Fixes in GDB 7.7.1" section of the gdb-7.7.x
release wiki page:
https://sourceware.org/gdb/wiki/GDB_7.7_Release
You will probably need to create a PR number to add the entry.
Thank you,
--
Joel
next prev parent reply other threads:[~2014-04-10 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 16:30 Pierre Langlois
2014-04-10 17:38 ` Joel Brobecker
2014-04-10 17:41 ` Joel Brobecker [this message]
2014-04-11 9:29 ` Pierre Langlois
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=20140410174101.GA27126@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.langlois@embecosm.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