From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
GNU C Library <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH 24/24] Intel CET: Document --enable-cet
Date: Mon, 14 May 2018 19:48:00 -0000 [thread overview]
Message-ID: <afd3be62-d870-0082-6df9-3b5882abbf03@redhat.com> (raw)
In-Reply-To: <CAMe9rOqhPW+kG4udaVgeZAVg3O8spkmVwTLt=HXJeaYw5THk3w@mail.gmail.com>
On 05/14/2018 09:45 PM, H.J. Lu wrote:
> Like this?
Looks good, with one nit:
> + (SHSTK). CET-enabled glibc is compatible with all existing
Missing space after period.
> +with indirect branch tracking (IBT) and shadow stack (SHSTK). CET-enabled
You need to write â(SHSTK)@.â to add the missing space.
Thanks,
Florian
next prev parent reply other threads:[~2018-05-14 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 21:32 H.J. Lu
2018-05-14 17:44 ` Florian Weimer
2018-05-14 19:46 ` H.J. Lu
2018-05-14 19:48 ` Florian Weimer [this message]
2018-05-14 23:15 ` H.J. Lu
2018-06-13 15:32 [PATCH-V2: 00/24] CET: Prepare for CET enabling H.J. Lu
2018-06-13 15:32 ` [PATCH 24/24] Intel CET: Document --enable-cet H.J. Lu
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=afd3be62-d870-0082-6df9-3b5882abbf03@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/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).