From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Daniel Palmer <daniel@thingy.jp>
Cc: w@1wt.eu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tools/nolibc: Rename __no_stack_protector to __nolibc_no_stack_protector
Date: Mon, 27 Apr 2026 19:24:06 +0200 [thread overview]
Message-ID: <72f55fd7-4008-4668-871c-ba9572c751cc@t-8ch.de> (raw)
In-Reply-To: <20260425111315.3191461-2-daniel@thingy.jp>
On 2026-04-25 20:13:14+0900, Daniel Palmer wrote:
> To avoid polluting the namespace rename __no_stack_protector to
> __nolibc_no_stack_protector so its now within the nolibc umbrella.
Both patches applied, thanks!
> Suggested-by: Willy Tarreau <w@1wt.eu>
> Signed-off-by: Daniel Palmer <daniel@thingy.jp>
(...)
next prev parent reply other threads:[~2026-04-27 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 11:13 [PATCH 0/2] Small stack protector bits Daniel Palmer
2026-04-25 11:13 ` [PATCH 1/2] tools/nolibc: Rename __no_stack_protector to __nolibc_no_stack_protector Daniel Palmer
2026-04-27 17:24 ` Thomas Weißschuh [this message]
2026-04-25 11:13 ` [PATCH 2/2] tools/nolibc: Don't use stack protector before setting it up Daniel Palmer
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=72f55fd7-4008-4668-871c-ba9572c751cc@t-8ch.de \
--to=linux@weissschuh.net \
--cc=daniel@thingy.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®