From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] ARM: stricter __stack_chk_guard check during prologue
Date: Wed, 29 Oct 2014 13:12:00 -0000 [thread overview]
Message-ID: <20141029131217.GA8313@adacore.com> (raw)
In-Reply-To: <87wq7jtoqt.fsf@codesourcery.com>
> >>> Thanks! Attached is a revised patch. I will push it after you
> >>> fix the latent bug you noticed - just let me know when?
> >>
> >> I'll post the patch next Monday.
> >
> > For the record, I posted the patch here
> > https://sourceware.org/ml/gdb-patches/2014-10/msg00690.html
>
> Joel,
> I've pushed the patch in. You can push your patch in now.
Thank you, Yao. My patch is now in as well.
--
Joel
prev parent reply other threads:[~2014-10-29 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 14:22 over-permissive stack_chk_guard on ARM Joel Brobecker
2014-10-23 2:53 ` Yao Qi
2014-10-23 15:39 ` [RFA] ARM: stricter __stack_chk_guard check during prologue (was: "Re: over-permissive stack_chk_guard on ARM") Joel Brobecker
2014-10-24 8:29 ` [RFA] ARM: stricter __stack_chk_guard check during prologue Yao Qi
2014-10-24 12:23 ` Joel Brobecker
2014-10-24 12:48 ` Yao Qi
2014-10-27 6:26 ` Yao Qi
2014-10-29 5:48 ` Yao Qi
2014-10-29 13:12 ` 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=20141029131217.GA8313@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).