From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: James Greenhalgh <james.greenhalgh@arm.com>, gcc-patches@gcc.gnu.org
Cc: nd@arm.com, richard.earnshaw@arm.com, nickc@redhat.com,
ramana.radhakrishnan@arm.com
Subject: Re: [Patch ARM] Document the +crypto extension on CPUs.
Date: Fri, 14 Jul 2017 15:46:00 -0000 [thread overview]
Message-ID: <5968E738.5080903@foss.arm.com> (raw)
In-Reply-To: <1500047077-25672-1-git-send-email-james.greenhalgh@arm.com>
On 14/07/17 16:44, James Greenhalgh wrote:
> Hi,
>
> We don't document the list of CPU names which can take a +crypto extension
> in the ARM port. This patch fixes that oversight.
>
> OK?
Ok.
Thanks,
Kyrill
> Thanks,
> James
>
> ---
> 2017-14-07 James Greenhalgh <james.greenhalgh@arm.com>
>
> * doc/invoke.texi (arm/-mcpu): Document +crypto.
>
prev parent reply other threads:[~2017-07-14 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 15:45 James Greenhalgh
2017-07-14 15:46 ` Kyrill Tkachov [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=5968E738.5080903@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=nd@arm.com \
--cc=nickc@redhat.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).