From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH v3 0/3] use wincap in format_proc_cpuinfo for user_shstk
Date: Fri, 16 Jun 2023 21:51:02 +0200 [thread overview]
Message-ID: <ZIy9JuA2wxH4i37A@calimero.vinschen.de> (raw)
In-Reply-To: <cover.1686934096.git.Brian.Inglis@Shaw.ca>
Hi Brian,
On Jun 16 11:17, Brian Inglis wrote:
> Fixes: 41fdb869f998 "fhandler/proc.cc(format_proc_cpuinfo): Add Linux 6.3 cpuinfo"
>
> In test for for AMD/Intel Control flow Enforcement Technology user mode
> shadow stack support replace Windows version tests with test of wincap
> member addition has_user_shstk with Windows version dependent value
>
> Signed-off-by: Brian Inglis <Brian.Inglis@Shaw.ca>
>
> Brian Inglis (3):
> wincap.h: add wincap member has_user_shstk
> wincap.cc: set wincap member has_user_shstk true for 2004+
> fhandler/proc.cc: use wincap.has_user_shstk
>
> winsup/cygwin/fhandler/proc.cc | 8 ++++----
> winsup/cygwin/local_includes/wincap.h | 2 ++
> winsup/cygwin/wincap.cc | 10 ++++++++++
> 3 files changed, 16 insertions(+), 4 deletions(-)
>
> --
> 2.39.0
Is that actually the final version? It's still missing the commit
message text explaining things and the "Fixes" line...
Thanks,
Corinna
next prev parent reply other threads:[~2023-06-16 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 17:17 Brian Inglis
2023-06-16 17:17 ` [PATCH v3 1/3] wincap.h: add wincap member has_user_shstk Brian Inglis
2023-06-16 17:17 ` [PATCH v3 2/3] wincap.cc: set wincap member has_user_shstk true for 2004+ Brian Inglis
2023-06-16 17:17 ` [PATCH v3 3/3] fhandler/proc.cc: use wincap.has_user_shstk Brian Inglis
2023-06-16 19:51 ` Corinna Vinschen [this message]
2023-06-16 21:26 ` [PATCH v3 0/3] use wincap in format_proc_cpuinfo for user_shstk Brian Inglis
2023-06-19 8:55 ` Corinna Vinschen
2023-06-19 18:27 ` Brian Inglis
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=ZIy9JuA2wxH4i37A@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.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).