From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Langlois <pierre.langlois@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][PR/backtrace 16721] Fix erroneous backtrace on AVR
Date: Fri, 21 Mar 2014 17:20:00 -0000 [thread overview]
Message-ID: <20140321171957.GK4282@adacore.com> (raw)
In-Reply-To: <532C3D3B.7040509@embecosm.com>
> Sorry for the late reply.
No worries.
> I am doing this work on behalf of Embecosm, we have an FSF copyright
> assignment on file.
Perfect!
> > * avr-tdep.c (avr_scan_prologue): Accept push r1 instruction for small
> > stack allocation.
I can push this patch for you, but you now also meet the requirements
for write access to the GDB repository (FSF assignment + 1 good patch).
If you are planning on contributing more patches, I suggest we get you
write access and let you commit yourself. WDYT? If not interested, just
let me know and I will push the patch. Otherwise, can you contact me
in private for further instructions on how to achieve that?
Thanks,
--
Joel
prev parent reply other threads:[~2014-03-21 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 17:53 Pierre Langlois
2014-03-19 8:00 ` Tristan Gingold
2014-03-19 12:34 ` Joel Brobecker
2014-03-21 13:23 ` Pierre Langlois
2014-03-21 17:20 ` Joel Brobecker [this message]
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=20140321171957.GK4282@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