From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-patches@cygwin.com
Subject: [PATCH v4 1/3] wincap.h: add wincap member has_user_shstk
Date: Mon, 19 Jun 2023 12:15:17 -0600 [thread overview]
Message-ID: <91439aaa378c5ed38b236ddb16b99644284b7fe1.1687198150.git.Brian.Inglis@Shaw.ca> (raw)
In-Reply-To: <cover.1687198150.git.Brian.Inglis@Shaw.ca>
Fixes: 41fdb869f998 fhandler/proc.cc(format_proc_cpuinfo): Add Linux 6.3 cpuinfo
Signed-off-by: Brian Inglis <Brian.Inglis@Shaw.ca>
---
winsup/cygwin/local_includes/wincap.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/winsup/cygwin/local_includes/wincap.h b/winsup/cygwin/local_includes/wincap.h
index 29a7a63de7f6..c14872787ca2 100644
--- a/winsup/cygwin/local_includes/wincap.h
+++ b/winsup/cygwin/local_includes/wincap.h
@@ -32,6 +32,7 @@ struct wincaps
unsigned has_linux_tcp_keepalive_sockopts : 1;
unsigned has_tcp_maxrtms : 1;
unsigned has_con_broken_tabs : 1;
+ unsigned has_user_shstk : 1;
};
};
@@ -84,6 +85,7 @@ public:
bool IMPLEMENT (has_linux_tcp_keepalive_sockopts)
bool IMPLEMENT (has_tcp_maxrtms)
bool IMPLEMENT (has_con_broken_tabs)
+ bool IMPLEMENT (has_user_shstk)
void disable_case_sensitive_dirs ()
{
--
2.39.0
next prev parent reply other threads:[~2023-06-19 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 18:15 [PATCH v4 0/3] use wincap in format_proc_cpuinfo for user_shstk Brian Inglis
2023-06-19 18:15 ` Brian Inglis [this message]
2023-06-19 18:15 ` [PATCH v4 2/3] wincap.cc: set wincap member has_user_shstk true for 2004+ Brian Inglis
2023-06-19 18:15 ` [PATCH v4 3/3] fhandler/proc.cc: use wincap.has_user_shstk Brian Inglis
2023-06-20 8:22 ` [PATCH v4 0/3] use wincap in format_proc_cpuinfo for user_shstk Corinna Vinschen
2023-06-21 4:50 ` Brian Inglis
2023-06-21 8:22 ` Corinna Vinschen
2023-06-21 15:04 ` 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=91439aaa378c5ed38b236ddb16b99644284b7fe1.1687198150.git.Brian.Inglis@Shaw.ca \
--to=brian.inglis@shaw.ca \
--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).