From: Eli Zaretskii <eliz@gnu.org>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: gdb-patches@sourceware.org, nd@arm.com
Subject: Re: [PATCH v2 1/8] AArch64: Add pointer authentication feature
Date: Wed, 06 Mar 2019 15:36:00 -0000 [thread overview]
Message-ID: <83mum8c8vx.fsf@gnu.org> (raw)
In-Reply-To: <20190306133325.2531-2-alan.hayward@arm.com> (message from Alan Hayward on Wed, 6 Mar 2019 13:33:34 +0000)
> From: Alan Hayward <Alan.Hayward@arm.com>
> CC: nd <nd@arm.com>, Alan Hayward <Alan.Hayward@arm.com>
> Date: Wed, 6 Mar 2019 13:33:34 +0000
>
> gdb/doc/ChangeLog:
>
> 2019-03-06 Alan Hayward <alan.hayward@arm.com>
> Jiong Wang <jiong.wang@arm.com>
>
> * gdb.texinfo: Describe pauth feature.
This part is OK, but please mention the name of the node where you are
making the changes, as if it were a function.
next prev parent reply other threads:[~2019-03-06 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 13:33 [PATCH v2 0/8] Support for AArch64 Pointer Authentication Alan Hayward
2019-03-06 13:33 ` [PATCH v2 8/8] AArch64: Read pauth section from core files Alan Hayward
2019-03-06 13:33 ` [PATCH v2 3/8] AArch64: Read pauth registers Alan Hayward
2019-03-21 20:56 ` Simon Marchi
2019-03-06 13:33 ` [PATCH v2 4/8] AArch64: gdbserver: read " Alan Hayward
2019-03-21 21:03 ` Simon Marchi
2019-03-06 13:33 ` [PATCH v2 1/8] AArch64: Add pointer authentication feature Alan Hayward
2019-03-06 15:36 ` Eli Zaretskii [this message]
2019-03-06 13:33 ` [PATCH v2 6/8] AArch64: DWARF unwinder support for signed return addresses Alan Hayward
2019-03-06 13:33 ` [PATCH v2 7/8] AArch64: Prologue scan " Alan Hayward
2019-03-06 13:33 ` [PATCH v2 5/8] AArch64: Add pauth DWARF registers Alan Hayward
2019-03-06 13:33 ` [PATCH v2 2/8] AArch64: Use HWCAP to detect pauth feature Alan Hayward
2019-03-21 20:51 ` Simon Marchi
2019-03-22 12:06 ` Alan Hayward
2019-03-14 12:34 ` [PATCH v2 0/8] Support for AArch64 Pointer Authentication Alan Hayward
2019-03-21 21:29 ` Simon Marchi
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=83mum8c8vx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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